gitlab-labkit 1.0.1 → 1.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1fcf883261bb809a67748d4f15c2a520ae392d3d069b5852cc20abf56e428b4e
-  data.tar.gz: ce56f2ec2b2dce0b420d0096ea6b4a48b54a91c350b802a245dcc0cae9219908
+  metadata.gz: 1bbb89ac1275f06d828f9d9fa4a24e20e33f4a01d201956d4dd8d30e87dd8f5a
+  data.tar.gz: 1d6b24a17f8b2096e34303fba306ea1271146b3245cb5edcb3fabbccd26f1e45
 SHA512:
-  metadata.gz: 70d57193fc2778250b004df0e39f7f98ff6f1bc5356d601f664b632cd6a7e9b4f2f772b6251406702b5cea84bda6fed02ad29d1ca196f2b29462e4887ded4b6e
-  data.tar.gz: 1cd77a020fe80b311512acf08b433913f0e9a06edce05a10961c018c19a1270c9420b477731cb88d4ceb5b641ee0a6d0ad4c34fc1bee528d2febae1f83a521dd
+  metadata.gz: 4950f9c1615b432b5d53ab54a51cca84a10cbf548b434665fdda93a2204f912f172540652df7b634907c61fa88f03f50a1ad9de96e04d2795a59393fe3fdcf93
+  data.tar.gz: a67c2262dd119373431f271779baf8311c5eb47a794a2970e1b4b9dcd28c59a4253ff844654f20a99026f95aabe6538f8fbdc864da29f007cd6c94a99eb427ad

data/.copier-answers.yml

@@ -3,7 +3,7 @@
 # See the project for instructions on how to update the project
 #
 # Changes here will be overwritten by Copier; NEVER EDIT MANUALLY
-_commit: v1.36.0
+_commit: v1.38.0
 _src_path: https://gitlab.com/gitlab-com/gl-infra/common-template-copier.git
 ee_licensed: false
 golang: false

data/.gitlab-ci-asdf-versions.yml

@@ -1,5 +1,5 @@
 # DO NOT MANUALLY EDIT; Run ./scripts/update-asdf-version-variables.sh to update this
 variables:
-    GL_ASDF_RUBY_VERSION: "3.4.7"
+    GL_ASDF_RUBY_VERSION: "3.4.8"
     GL_ASDF_SHELLCHECK_VERSION: "0.11"
     GL_ASDF_SHFMT_VERSION: "3.12"

data/.gitlab-ci.yml

@@ -19,13 +19,13 @@ include:
   # It includes standard checks, gitlab-scanners, validations and release processes
   # common to all projects using this template library.
   # see https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/blob/main/templates/standard.md
-  - component: $CI_SERVER_FQDN/gitlab-com/gl-infra/common-ci-tasks/standard-build@v2.78
+  - component: $CI_SERVER_FQDN/gitlab-com/gl-infra/common-ci-tasks/standard-build@v3.4
 
   # Runs rspec tests and rubocop on the project
   # see https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/blob/main/templates/ruby.md
-  - component: $CI_SERVER_FQDN/gitlab-com/gl-infra/common-ci-tasks/ruby-build@v2.78
+  - component: $CI_SERVER_FQDN/gitlab-com/gl-infra/common-ci-tasks/ruby-build@v3.4
 
-  - component: $CI_SERVER_FQDN/gitlab-com/gl-infra/common-ci-tasks/danger@v2.78
+  - component: $CI_SERVER_FQDN/gitlab-com/gl-infra/common-ci-tasks/danger@v3.4
 
 .test_template: &test_definition
   extends: .with_bundle

data/.pre-commit-config.yaml

@@ -25,7 +25,7 @@ repos:
   # Documentation available at
   # https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/blob/main/docs/pre-commit.md
   - repo: https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks
-    rev: v3.0  # renovate:managed
+    rev: v3.4  # renovate:managed
 
     hooks:
       - id: shellcheck  # Run shellcheck for changed Shell files

data/.tool-versions

@@ -1,3 +1,3 @@
-ruby 3.4.7
+ruby 3.4.8
 shfmt 3.12
 shellcheck 0.11

data/config/user_experience_slis/schema.json

@@ -1,5 +1,5 @@
 {
-  "$schema": "http://json-schema.org/draft-06/schema#",
+  "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://gitlab.com/gitlab-org/ruby/gems/labkit-ruby/-/raw/master/config/user_experience_slis/schema.json",
   "title": "User Experience SLI Definition",
   "description": "Schema for GitLab User Experience SLI files",
@@ -12,8 +12,8 @@
     },
     "feature_category": {
       "type": "string",
-      "minLength": 1,
-      "description": "GitLab feature category this experience belongs to"
+      "description": "GitLab feature category this experience belongs to",
+      "$ref": "https://gitlab.com/gitlab-org/gitlab/-/raw/master/config/feature_categories/schema.json"
     },
     "urgency": {
       "type": "string",

data/doc/architecture/decisions/001_field_standardization_dynamic_runtime_linting.md

@@ -0,0 +1,124 @@
+---
+owning-stage: '~devops::developer experience'
+description: 'Logging Field Standardization: Dynamic Runtime Linting'
+---
+
+# Logging Field Standardization ADR: Dynamic Runtime Linting
+
+## Context
+
+GitLab is implementing a [logging field standardization initiative](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/observability_field_standardisation/) to ensure logs are queryable and actionable across all systems. We need a mechanism to identify and track deprecated or non-standard logging fields across multiple codebases.
+
+### Requirements
+
+The solution must:
+
+1. Detect deprecated fields at the point of emission (runtime).
+1. Provide immediate feedback to developers (shift-left).
+1. Prevent new violations without blocking existing work.
+1. Support gradual migration from deprecated to standard fields.
+1. Never affect production performance.
+1. Provide clear guidance on standard field replacements.
+
+### The problem with static analysis
+
+We initially considered RuboCop (static linting), but this approach is inadequate due to Ruby's [dynamic and complex field construction](https://gitlab.com/gitlab-org/gitlab/-/blob/cfd4fb97968d1f7d30f39f89740e414e9437063a/lib/bulk_imports/logger.rb#L46).
+
+Static analysis can't reliably detect:
+
+- Fields merged from hash arguments.
+- Dynamically constructed field names.
+- Fields passed through multiple abstraction layers.
+- Conditional field inclusion based on runtime state.
+
+## Decision
+
+Implement dynamic runtime linting to validate logging fields as they're emitted during development and testing, rather than using static analysis.
+
+The validator will:
+
+- Intercept logging calls at runtime to detect deprecated fields.
+- Compare detected violations against a frozen baseline of known violations.
+- Raise an error on new violations while ignoring tracked existing tracked violations.
+- Provide immediate feedback to developers during local development.
+- Never affect production performance.
+
+## Consequences
+
+### Benefits
+
+- **Shift-left feedback**: Developers discover violations during local development, not in code review.
+- **Comprehensive detection**: Captures violations from all code execution paths (tests, Rake tasks, console, development environments).
+- **Accurate detection**: Runtime interception catches dynamically constructed fields that static analysis misses.
+- **Non-blocking**: Existing violations don't prevent development. They're tracked explicitly in baseline.
+- **Regression prevention**: CI fails on new violations, preventing deprecated fields from reappearing.
+- **Clear guidance**: Exact replacement field suggested for each violation.
+- **Zero production impact**: Validation only runs in development and test environments.
+
+### Trade-offs
+
+- **Execution path dependency**: Only detects violations in code paths that execute during the process.
+- **Runtime overhead**: Adds interception to all non-production processes.
+- **At-exit reporting**: Violations not visible until process completes.
+- **Baseline maintenance**: YAML files require updates when violations are fixed or added.
+- **Learning curve**: Developers must understand baseline management.
+- **File-level scoping**: Multiple violations in the same file are tracked together, making partial fixes during test runs challenging.
+
+### Risks and mitigations
+
+| Risk | Mitigation |
+|------|------------|
+| Limited code path coverage misses violations | Use Kibana to identify fields in production logs, run comprehensive test suites, use development server testing |
+| Baseline drift across branches | Clear documentation, automated baseline regeneration support |
+| At-exit reporting missed if process crashes | Violations still prevented in CI where processes complete successfully |
+
+## Alternatives
+
+### Alternative 1: Static analysis with RuboCop
+
+Use custom RuboCop cops to detect deprecated field usage.
+
+Rejected because:
+
+- Can't handle fields merged from hash variables.
+- Would produce many false negatives.
+- Complex pattern matching still misses dynamic cases.
+- Poor developer experience with unclear violations.
+
+### Alternative 2: Manual tracking
+
+Track violations in spreadsheets or GitLab issues.
+
+Rejected because:
+
+- No automated enforcement or detection.
+- Manual process becomes stale quickly.
+- No shift-left feedback to developers.
+- Can't prevent regressions.
+
+### Alternative 3: Grep-based CI checks
+
+Search source code for deprecated field strings in CI.
+
+Rejected because:
+
+- High false positive rate (matches in comments, strings, tests).
+- Can't distinguish field usage from definitions.
+- No stable tracking across refactoring.
+- Poor user experience with unclear error messages.
+
+### Alternative 4: Production log analysis only
+
+Rely solely on Kibana analysis to find deprecated fields.
+
+Rejected because:
+
+- No prevention, only reactive detection.
+- Violations already in production when discovered.
+- No developer feedback during development.
+- Difficult to trace back to specific code locations.
+
+## References
+
+- [Parent Epic](https://gitlab.com/groups/gitlab-org/quality/-/work_items/235)
+- [Observability Field Standardisation](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/observability_field_standardisation/)

data/gitlab-labkit.gemspec

@@ -25,10 +25,11 @@ Gem::Specification.new do |spec|
   spec.add_runtime_dependency "grpc", ">= 1.75" # Be sure to update the "grpc-tools" dev_dependency too
   spec.add_runtime_dependency "google-protobuf", ">= 3.25", "< 5.0"
   spec.add_runtime_dependency "jaeger-client", "~> 1.1.0"
-  spec.add_runtime_dependency 'json-schema', '~> 5.1'
+  spec.add_runtime_dependency 'json_schemer', '>= 2.3.0', '< 3.0'
+  spec.add_runtime_dependency "openssl", "~> 3.3.2"
   spec.add_runtime_dependency "opentracing", "~> 0.4"
   spec.add_runtime_dependency "pg_query", ">= 6.1.0", "< 7.0"
-  spec.add_runtime_dependency "prometheus-client-mmap", "~> 1.2.9"
+  spec.add_runtime_dependency "prometheus-client-mmap", ">= 1.2", "< 2.0"
   spec.add_runtime_dependency "redis", "> 3.0.0", "< 6.0.0"
 
   # Please maintain alphabetical order for dev dependencies

data/lib/labkit/json_schema/README.md

@@ -0,0 +1,74 @@
+# JSON Schema Reference Resolver
+
+## Overview
+
+The `RefResolver` class provides HTTP/HTTPS-based resolution for external JSON schema references. It enables validation of JSON data against schemas that reference remote schema definitions, with built-in caching and timeout protection.
+
+## Why Use RefResolver?
+
+When working with JSON schemas, you may encounter `$ref` properties that point to external schema definitions hosted remotely:
+
+```json
+{
+  "$ref": "https://example.com/schemas/common.json#/definitions/address"
+}
+```
+
+The `RefResolver` solves several key challenges:
+
+- **Remote Schema Resolution**: Automatically fetches and parses external schema definitions over HTTP/HTTPS
+- **Performance Optimization**: Caches fetched schemas to avoid redundant network requests
+- **Reliability**: Implements configurable timeouts to prevent hanging on slow or unresponsive endpoints
+- **Error Handling**: Provides clear error messages for network failures, timeouts, and invalid JSON responses
+
+## How to Use
+
+### Basic Usage
+
+The `RefResolver` is designed to work with the [JSONSchemer](https://github.com/davishmcclurg/json_schemer) gem:
+
+```ruby
+require 'labkit/json_schema/ref_resolver'
+
+# Create a resolver instance
+resolver = Labkit::JsonSchema::RefResolver.new
+
+# Use with JSONSchemer
+schema = JSONSchemer.schema(
+  your_schema_hash,
+  ref_resolver: resolver
+)
+
+# Validate data
+schema.valid?(your_data)
+```
+
+### Custom Timeout Configuration
+
+By default, the resolver uses a 2-second timeout for both connection and read operations. You can customize this:
+
+```ruby
+# Use a 5-second timeout
+resolver = Labkit::JsonSchema::RefResolver.new(timeout_s: 5)
+```
+
+### Cache Management
+
+The resolver maintains a class-level cache to share fetched schemas across instances:
+
+```ruby
+# Access the cache
+Labkit::JsonSchema::RefResolver.cache
+
+# Clear the cache if needed
+Labkit::JsonSchema::RefResolver.cache.clear
+```
+
+## Use Case Example
+
+The `RefResolver` is used in the User Experience SLI Registry [lib/labkit/user_experience_sli/registry.rb](lib/labkit/user_experience_sli/registry.rb) to validate user experience definitions against a JSON schema.
+
+## Implementation Details
+
+- Only HTTP and HTTPS schemes are supported. Other schemes (FTP, file://, etc.) will raise an error.
+- The class-level cache is shared across all instances. In multi-threaded environments, consider using appropriate synchronization mechanisms if cache consistency is critical.

data/lib/labkit/json_schema/ref_resolver.rb

@@ -0,0 +1,63 @@
+# frozen_string_literal: true
+
+require 'net/http'
+require 'uri'
+require 'json'
+
+module Labkit
+  module JsonSchema
+    # This class resolves JSON schema references (e.g., "$ref": "http://example.com/schema.json")
+    # by fetching remote schemas over HTTP/HTTPS and caching them.
+    # It is used by JSONSchemer to resolve external schema definitions.
+    # We need it to validate JSON data against schemas that might be hosted remotely.
+    class RefResolver
+      mattr_accessor :cache, default: {}
+
+      def initialize(timeout_s: 2)
+        @timeout_s = timeout_s
+      end
+
+      def call(uri)
+        uri_str = uri.to_s
+
+        return cache[uri_str] if cache.key?(uri_str)
+
+        cache[uri_str] = fetch_remote_schema(uri_str)
+      end
+
+      private
+
+      def fetch_remote_schema(uri_str)
+        uri = URI(uri_str)
+
+        raise(JSONSchemer::UnknownRef, "Unsupported URI scheme: #{uri_str}") unless %w[http https].include?(uri.scheme)
+
+        response = Net::HTTP.start(
+          uri.host,
+          uri.port,
+          use_ssl: uri.scheme == 'https',
+          open_timeout: @timeout_s,
+          read_timeout: @timeout_s
+        ) do |http|
+          request = Net::HTTP::Get.new(uri.request_uri)
+          http.request(request)
+        end
+
+        unless response.is_a?(Net::HTTPSuccess)
+          raise(
+            JSONSchemer::UnknownRef,
+            "Failed to fetch #{uri_str}: #{response.code} #{response.message}"
+          )
+        end
+
+        JSON.parse(response.body)
+      rescue Net::OpenTimeout, Net::ReadTimeout => e
+        raise(JSONSchemer::UnknownRef, "Timeout fetching #{uri_str}: #{e.message}")
+      rescue JSON::ParserError => e
+        raise(JSONSchemer::UnknownRef, "Invalid JSON at #{uri_str}: #{e.message}")
+      rescue SocketError, Errno::ECONNREFUSED => e
+        raise(JSONSchemer::UnknownRef, "Connection failed for #{uri_str}: #{e.message}")
+      end
+    end
+  end
+end

data/lib/labkit/logging/json_logger.rb

@@ -1,5 +1,6 @@
 # frozen_string_literal: true
 require "time"
+require "date"
 require "logger"
 require "json"
 
@@ -37,6 +38,12 @@ module Labkit
       end
 
       def format_message(severity, timestamp, progname, message)
+        data = format_data(severity, timestamp, progname, message)
+
+        dump_json(data) << "\n"
+      end
+
+      def format_data(severity, timestamp, progname, message)
         data = default_attributes
         data[:severity] = severity
         data[:time] = timestamp.utc.iso8601(3)
@@ -52,11 +59,10 @@ module Labkit
           data[:message] = message
         when Hash
           reject_reserved_log_keys!(message)
-          format_time!(data)
           data.merge!(message)
         end
 
-        dump_json(data) << "\n"
+        data
       end
 
       private
@@ -78,16 +84,6 @@ module Labkit
                   "\n\nUse key names that are descriptive e.g. by using a prefix."
         end
       end
-
-      def format_time!(hash)
-        hash.each do |key, value|
-          if value.is_a?(Time)
-            hash[key] = value.utc.iso8601(3)
-          elsif value.is_a?(Hash)
-            format_time!(value)
-          end
-        end
-      end
     end
   end
 end

data/lib/labkit/user_experience_sli/README.md

@@ -33,6 +33,23 @@ This allows you to:
 
 **Note:** The registry is automatically reset when the configuration changes, so the new path takes effect immediately.
 
+### RefResolver Timeout Configuration
+
+When validating user experience SLI definitions against JSON schemas, the system may need to fetch remote schema references over HTTP/HTTPS. By default, the timeout for these requests is 2 seconds. You can configure a custom timeout:
+
+```ruby
+Labkit::UserExperienceSli.configure do |config|
+  config.ref_resolver_timeout = 5  # Set timeout to 5 seconds
+end
+```
+
+This configuration is useful when:
+- Working in environments with slower network connections
+- Fetching schemas from remote servers with higher latency
+- Needing stricter timeout constraints for faster failure detection
+
+**Note:** The timeout applies to both connection opening and reading operations when fetching remote JSON schema references.
+
 ### User Experience Definitions
 
 User Experience SLI definitions will be lazy loaded from the default directory (`config/user_experience_slis`).

data/lib/labkit/user_experience_sli/experience.rb

@@ -236,9 +236,9 @@ module Labkit
           user_experience_id: id,
           feature_category: @definition.feature_category,
           urgency: @definition.urgency,
-          start_time: @start_time,
-          checkpoint_time: @checkpoint_time,
-          end_time: @end_time,
+          start_time: @start_time&.iso8601(3),
+          checkpoint_time: @checkpoint_time&.iso8601(3),
+          end_time: @end_time&.iso8601(3),
           elapsed_time_s: elapsed_time,
           urgency_threshold_s: urgency_threshold
         )

data/lib/labkit/user_experience_sli/registry.rb

@@ -1,9 +1,10 @@
 # frozen_string_literal: true
 
 require 'forwardable'
-require 'json-schema'
+require 'json_schemer'
 require 'pathname'
 require 'yaml'
+require 'labkit/json_schema/ref_resolver'
 
 module Labkit
   module UserExperienceSli
@@ -77,8 +78,7 @@ module Labkit
         content = YAML.safe_load(file_path.read)
         return nil unless content.is_a?(Hash)
 
-        errors = JSON::Validator.fully_validate(schema, content)
-        return Definition.new(user_experience_id: experience_id, **content) if errors.empty?
+        return Definition.new(user_experience_id: experience_id, **content) if schema.valid?(content)
 
         warn("Invalid schema for #{file_path}")
 
@@ -90,7 +90,11 @@ module Labkit
       end
 
       def schema
-        @schema ||= JSON.parse(File.read(SCHEMA_PATH))
+        @schema ||= begin
+          schema = JSON.parse(File.read(SCHEMA_PATH))
+          timeout = Labkit::UserExperienceSli.configuration.ref_resolver_timeout
+          JSONSchemer.schema(schema, ref_resolver: Labkit::JsonSchema::RefResolver.new(timeout_s: timeout))
+        end
       end
 
       def warn(message)

data/lib/labkit/user_experience_sli.rb

@@ -16,11 +16,12 @@ module Labkit
   module UserExperienceSli
     # Configuration class for UserExperienceSli
     class Configuration
-      attr_accessor :logger, :registry_path
+      attr_accessor :logger, :registry_path, :ref_resolver_timeout
 
       def initialize
         @logger = Labkit::Logging::JsonLogger.new($stdout)
         @registry_path = File.join("config", "user_experience_slis")
+        @ref_resolver_timeout = 2
       end
     end
 

data/scripts/prepare-dev-env.sh

@@ -53,8 +53,11 @@ fi
 
 # install mise/asdf dependencies
 echo "installing required plugins with mise install.."
-mise plugins update
+mise plugins update -q
 mise install
+
+# set PROMPT_COMMAND to empty value for mise if unset
+: "${PROMPT_COMMAND:=}"
 eval "$(mise activate bash)"
 
 # pre-commit is optional

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: gitlab-labkit
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.1.3
 platform: ruby
 authors:
 - Andrew Newdigate
@@ -98,19 +98,39 @@ dependencies:
       - !ruby/object:Gem::Version
         version: 1.1.0
 - !ruby/object:Gem::Dependency
-  name: json-schema
+  name: json_schemer
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.3.0
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.3.0
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+- !ruby/object:Gem::Dependency
+  name: openssl
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '5.1'
+        version: 3.3.2
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '5.1'
+        version: 3.3.2
 - !ruby/object:Gem::Dependency
   name: opentracing
   requirement: !ruby/object:Gem::Requirement
@@ -149,16 +169,22 @@ dependencies:
   name: prometheus-client-mmap
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '1.2'
+    - - "<"
       - !ruby/object:Gem::Version
-        version: 1.2.9
+        version: '2.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: 1.2.9
+        version: '1.2'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '2.0'
 - !ruby/object:Gem::Dependency
   name: redis
   requirement: !ruby/object:Gem::Requirement
@@ -455,6 +481,7 @@ files:
 - Rakefile
 - config/user_experience_slis/schema.json
 - config/user_experience_slis/testing_sample.yml
+- doc/architecture/decisions/001_field_standardization_dynamic_runtime_linting.md
 - gitlab-labkit.gemspec
 - lib/gitlab-labkit.rb
 - lib/labkit/context.rb
@@ -468,6 +495,8 @@ files:
 - lib/labkit/fields.rb
 - lib/labkit/fips.rb
 - lib/labkit/httpclient_publisher.rb
+- lib/labkit/json_schema/README.md
+- lib/labkit/json_schema/ref_resolver.rb
 - lib/labkit/logging.rb
 - lib/labkit/logging/grpc.rb
 - lib/labkit/logging/grpc/server_interceptor.rb
@@ -539,7 +568,6 @@ files:
 - lib/labkit/user_experience_sli/null.rb
 - lib/labkit/user_experience_sli/registry.rb
 - renovate.json
-- scripts/install-asdf-plugins.sh
 - scripts/prepare-dev-env.sh
 - scripts/update-asdf-version-variables.sh
 homepage: https://gitlab.com/gitlab-org/labkit-ruby

data/scripts/install-asdf-plugins.sh

@@ -1,13 +0,0 @@
-#!/usr/bin/env bash
-# Vendored from https://gitlab.com/gitlab-com/gl-infra/common-template-copier
-# Consider contributing upstream when updating this file
-
-# This file is deprecated: going forward running `mise install` should be sufficient.
-
-set -euo pipefail
-IFS=$'\n\t'
-
-echo >&2 -e "2024-08-07: this file is deprecated: going forward, simply run 'mise install' to install plugins."
-echo >&2 -e "Recommended reading: https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/blob/main/docs/developer-setup.md"
-
-mise install