Geo: Replicate Dependency Proxy Manifests

Replicate Dependency Proxy Manifests

This issue is for implementing Geo replication and verification of Dependency Proxy Manifests.

For more background, see Geo self-service framework.

In order to implement and test this feature, you need to first set up Geo locally.

There are three main sections below. It is a good idea to structure your merge requests this way as well:

1. Modify database schemas to prepare to add Geo support for Dependency Proxy Manifests
2. Implement Geo support of Dependency Proxy Manifests behind a feature flag
3. Release Geo support of Dependency Proxy Manifests

It is also a good idea to first open a proof-of-concept merge request. It can be helpful for working out kinks and getting initial support and feedback from the Geo team. As an example, see the Proof of Concept to replicate Pipeline Artifacts.

You can look into the following examples of MRs for implementing replication/verification for a new blob type:

• Add db changes and add verification for MR diffs using SSF
• Verify Terraform state versions
• Verify LFS objects

Modify database schemas to prepare to add Geo support for Dependency Proxy Manifests

You might do this section in its own merge request, but it is not required.

Add the registry table to track replication and verification state

Geo secondary sites have a Geo tracking database independent of the main database. It is used to track the replication and verification state of all replicables. Every Model has a corresponding "registry" table in the Geo tracking database.

• Create the migration file in ee/db/geo/migrate:

  bin/rails generate migration CreateDependencyProxyManifestRegistry --database geo

• Replace the contents of the migration file with the following. Note that we cannot add a foreign key constraint on dependency_proxy_manifest_id because the dependency_proxy_manifests table is in a different database. The application code must handle logic such as propagating deletions.

  # frozen_string_literal: true
  
  class CreateDependencyProxyManifestRegistry < Gitlab::Database::Migration[2.0]
    def change
      create_table :dependency_proxy_manifest_registry, id: :bigserial, force: :cascade do |t|
        t.bigint :dependency_proxy_manifest_id, null: false
        t.datetime_with_timezone :created_at, null: false
        t.datetime_with_timezone :last_synced_at
        t.datetime_with_timezone :retry_at
        t.datetime_with_timezone :verified_at
        t.datetime_with_timezone :verification_started_at
        t.datetime_with_timezone :verification_retry_at
        t.integer :state, default: 0, null: false, limit: 2
        t.integer :verification_state, default: 0, null: false, limit: 2
        t.integer :retry_count, default: 0, limit: 2, null: false
        t.integer :verification_retry_count, default: 0, limit: 2, null: false
        t.boolean :checksum_mismatch, default: false, null: false
        t.binary :verification_checksum
        t.binary :verification_checksum_mismatched
        t.text :verification_failure, limit: 255
        t.text :last_sync_failure, limit: 255
  
        t.index :dependency_proxy_manifest_id, name: :index_dependency_proxy_manifest_registry_on_dependency_proxy_manifest_id, unique: true
        t.index :retry_at
        t.index :state
        # To optimize performance of DependencyProxyManifestRegistry.verification_failed_batch
        t.index :verification_retry_at, name: :dependency_proxy_manifest_registry_failed_verification, order: "NULLS FIRST", where: "((state = 2) AND (verification_state = 3))"
        # To optimize performance of DependencyProxyManifestRegistry.needs_verification_count
        t.index :verification_state, name: :dependency_proxy_manifest_registry_needs_verification, where: "((state = 2) AND (verification_state = ANY (ARRAY[0, 3])))"
        # To optimize performance of DependencyProxyManifestRegistry.verification_pending_batch
        t.index :verified_at, name: :dependency_proxy_manifest_registry_pending_verification, order: "NULLS FIRST", where: "((state = 2) AND (verification_state = 0))"
      end
    end
  end

• If deviating from the above example, then be sure to order columns according to our guidelines.

• Add the new table to the GitLab Schema defined in ee/lib/ee/gitlab/database/gitlab_schemas.yml.

  dependency_proxy_manifest_registry: :gitlab_geo

• Run Geo tracking database migrations:

  bin/rake db:migrate:geo

• Be sure to commit the relevant changes in ee/db/geo/structure.sql

Add verification state fields on the Geo primary site

The Geo primary site needs to checksum every replicable so secondaries can verify their own checksums. To do this, Geo requires fields on the Model. Add verification state fields to a separate table. Consult a database expert if needed.

Add verification state fields to a new table

• Create the migration file in db/migrate:

  bin/rails generate migration CreateDependencyProxyManifestStates

• Replace the contents of the migration file with:

  # frozen_string_literal: true
  
  class CreateDependencyProxyManifestStates < Gitlab::Database::Migration[2.0]
    VERIFICATION_STATE_INDEX_NAME = "index_dependency_proxy_manifest_states_on_verification_state"
    PENDING_VERIFICATION_INDEX_NAME = "index_dependency_proxy_manifest_states_pending_verification"
    FAILED_VERIFICATION_INDEX_NAME = "index_dependency_proxy_manifest_states_failed_verification"
    NEEDS_VERIFICATION_INDEX_NAME = "index_dependency_proxy_manifest_states_needs_verification"
  
    enable_lock_retries!
  
    def up
      create_table :dependency_proxy_manifest_states, id: false do |t|
        t.datetime_with_timezone :verification_started_at
        t.datetime_with_timezone :verification_retry_at
        t.datetime_with_timezone :verified_at
        t.references :dependency_proxy_manifest, primary_key: true, default: nil, index: false, foreign_key: { on_delete: :cascade }
        t.integer :verification_state, default: 0, limit: 2, null: false
        t.integer :verification_retry_count, limit: 2
        t.binary :verification_checksum, using: 'verification_checksum::bytea'
        t.text :verification_failure, limit: 255
  
        t.index :verification_state, name: VERIFICATION_STATE_INDEX_NAME
        t.index :verified_at, where: "(verification_state = 0)", order: { verified_at: 'ASC NULLS FIRST' }, name: PENDING_VERIFICATION_INDEX_NAME
        t.index :verification_retry_at, where: "(verification_state = 3)", order: { verification_retry_at: 'ASC NULLS FIRST' }, name: FAILED_VERIFICATION_INDEX_NAME
        t.index :verification_state, where: "(verification_state = 0 OR verification_state = 3)", name: NEEDS_VERIFICATION_INDEX_NAME
      end
    end
  
    def down
      drop_table :dependency_proxy_manifest_states
    end
  end

• If deviating from the above example, then be sure to order columns according to our guidelines.

• Add the new table to the GitLab Schema defined in lib/gitlab/database/gitlab_schemas.yml with the databases they need to be added to.

  dependency_proxy_manifest_states: :gitlab_main

• Run database migrations:

  bin/rake db:migrate

• If dependency_proxy_manifests is a high-traffic table, follow the database documentation to use with_lock_retries

• Be sure to commit the relevant changes in db/structure.sql

That's all of the required database changes.

Implement Geo support of Dependency Proxy Manifests behind a feature flag

Step 1. Implement replication and verification

• Add the following lines to the dependency_proxy_manifest model to accomplish some important tasks:

  • Include ::Geo::ReplicableModel in the DependencyProxyManifest class, and specify the Replicator class with_replicator Geo::DependencyProxyManifestReplicator.
  • Include the ::Geo::VerifiableModel concern.
  • Delegate verification related methods to the dependency_proxy_manifest_state model.
  • For verification, override some scopes to use the dependency_proxy_manifest_states table instead of the model table.
  • Implement the verification_state_object method to return the object that holds the verification details
  • Override some methods to use the dependency_proxy_manifest_states table in verification-related queries.

  At this point the DependencyProxyManifest class should look like this:

  # frozen_string_literal: true
  
  class DependencyProxyManifest < ApplicationRecord
    ...
    include ::Geo::ReplicableModel
    include ::Geo::VerifiableModel
  
    delegate(*::Geo::VerificationState::VERIFICATION_METHODS, to: :dependency_proxy_manifest_state)
  
    with_replicator Geo::DependencyProxyManifestReplicator
  
    mount_uploader :file, DependencyProxyManifestUploader
  
    has_one :dependency_proxy_manifest_state, autosave: false, inverse_of: :dependency_proxy_manifest, class_name: 'Geo::DependencyProxyManifestState'
  
    after_save :save_verification_details
  
    scope :with_verification_state, ->(state) { joins(:dependency_proxy_manifest_state).where(dependency_proxy_manifest_states: { verification_state: verification_state_value(state) }) }
    scope :checksummed, -> { joins(:dependency_proxy_manifest_state).where.not(dependency_proxy_manifest_states: { verification_checksum: nil } ) }
    scope :not_checksummed, -> { joins(:dependency_proxy_manifest_state).where(dependency_proxy_manifest_states: { verification_checksum: nil } ) }
  
    scope :available_verifiables, -> { joins(:dependency_proxy_manifest_state) }
  
    # Override the `all` default if not all records can be replicated. For an
    # example of an existing Model that needs to do this, see
    # `EE::MergeRequestDiff`.
    # scope :available_replicables, -> { all }
  
    def verification_state_object
      dependency_proxy_manifest_state
    end
    ...
  
    class_methods do
      extend ::Gitlab::Utils::Override
      ...
  
      # @param primary_key_in [Range, DependencyProxyManifest] arg to pass to primary_key_in scope
      # @return [ActiveRecord::Relation<DependencyProxyManifest>] everything that should be synced to this node, restricted by primary key
      def self.replicables_for_current_secondary(primary_key_in)
        # This issue template does not help you write this method.
        #
        # This method is called only on Geo secondary sites. It is called when
        # we want to know which records to replicate. This is not easy to automate
        # because for example:
        #
        # * The "selective sync" feature allows admins to choose which namespaces
        #   to replicate, per secondary site. Most Models are scoped to a
        #   namespace, but the nature of the relationship to a namespace varies
        #   between Models.
        # * The "selective sync" feature allows admins to choose which shards to
        #   replicate, per secondary site. Repositories are associated with
        #   shards. Most blob types are not, but Project Uploads are.
        # * Remote stored replicables are not replicated, by default. But the
        #   setting `sync_object_storage` enables replication of remote stored
        #   replicables.
        #
        # Search the codebase for examples, and consult a Geo expert if needed.
      end
  
      override :verification_state_table_class
      def verification_state_table_class
        DependencyProxyManifestState
      end
    end
  
    def dependency_proxy_manifest_state
      super || build_dependency_proxy_manifest_state
    end
  
    ...
  end

• Implement DependencyProxyManifest.replicables_for_current_secondary above.

• Ensure DependencyProxyManifest.replicables_for_current_secondary is well-tested. Search the codebase for replicables_for_current_secondary to find examples of parameterized table specs. You may need to add more FactoryBot traits.

• Add the following shared examples to ee/spec/models/ee/dependency_proxy_manifest_spec.rb:

    include_examples 'a replicable model with a separate table for verification state' do
      let(:verifiable_model_record) { build(:dependency_proxy_manifest) } # add extra params if needed to make sure the record is included in `available_verifiables`
      let(:unverifiable_model_record) { build(:dependency_proxy_manifest) } # add extra params if needed to make sure the record is NOT included in `available_verifiables`
    end

• Create ee/app/replicators/geo/dependency_proxy_manifest_replicator.rb. Implement the #carrierwave_uploader method which should return a CarrierWave::Uploader, and implement the class method .model to return the DependencyProxyManifest class:

  # frozen_string_literal: true
  
  module Geo
    class DependencyProxyManifestReplicator < Gitlab::Geo::Replicator
      include ::Geo::BlobReplicatorStrategy
      extend ::Gitlab::Utils::Override
  
      def self.model
        ::DependencyProxyManifest
      end
  
      def carrierwave_uploader
        model_record.file
      end
  
      override :verification_feature_flag_enabled?
      def self.verification_feature_flag_enabled?
        # We are adding verification at the same time as replication, so we
        # don't need to toggle verification separately from replication. When
        # the replication feature flag is off, then verification is also off
        # (see `VerifiableReplicator.verification_enabled?`)
        true
      end
  
    end
  end

• Generate the feature flag definition file by running the feature flag commands and following the command prompts:

  bin/feature-flag --ee geo_dependency_proxy_manifest_replication --type development --group 'group::geo'
  bin/feature-flag --ee geo_dependency_proxy_manifest_verification --type development --group 'group::geo'

• Add this replicator class to the method replicator_classes in ee/lib/gitlab/geo.rb:

  REPLICATOR_CLASSES = [
    ::Geo::PackageFileReplicator,
    ::Geo::DependencyProxyManifestReplicator
  ]
  end

• Create ee/spec/replicators/geo/dependency_proxy_manifest_replicator_spec.rb and perform the necessary setup to define the model_record variable for the shared examples:

  # frozen_string_literal: true
  
  require 'spec_helper'
  
  RSpec.describe Geo::DependencyProxyManifestReplicator do
    let(:model_record) { build(:dependency_proxy_manifest) }
  
    include_examples 'a blob replicator'
    include_examples 'a verifiable replicator'
  end

• Create ee/app/models/geo/dependency_proxy_manifest_registry.rb:

  # frozen_string_literal: true
  
  module Geo
    class DependencyProxyManifestRegistry < Geo::BaseRegistry
      include ::Geo::ReplicableRegistry
      include ::Geo::VerifiableRegistry
  
      MODEL_CLASS = ::DependencyProxyManifest
      MODEL_FOREIGN_KEY = :dependency_proxy_manifest_id
  
      belongs_to :dependency_proxy_manifest, class_name: 'DependencyProxyManifest'
    end
  end

• Update REGISTRY_CLASSES in ee/app/workers/geo/secondary/registry_consistency_worker.rb.

• Add a custom factory name if needed in def model_class_factory_name in ee/spec/support/helpers/ee/geo_helpers.rb.

• Update it 'creates missing registries for each registry class' in ee/spec/workers/geo/secondary/registry_consistency_worker_spec.rb.

• Add dependency_proxy_manifest_registry to ActiveSupport::Inflector.inflections in config/initializers_before_autoloader/000_inflections.rb.

• Create ee/spec/factories/geo/dependency_proxy_manifest_registry.rb:

  # frozen_string_literal: true
  
  FactoryBot.define do
    factory :geo_dependency_proxy_manifest_registry, class: 'Geo::DependencyProxyManifestRegistry' do
      dependency_proxy_manifest # This association should have data, like a file or repository
      state { Geo::DependencyProxyManifestRegistry.state_value(:pending) }
  
      trait :synced do
        state { Geo::DependencyProxyManifestRegistry.state_value(:synced) }
        last_synced_at { 5.days.ago }
      end
  
      trait :failed do
        state { Geo::DependencyProxyManifestRegistry.state_value(:failed) }
        last_synced_at { 1.day.ago }
        retry_count { 2 }
        last_sync_failure { 'Random error' }
      end
  
      trait :started do
        state { Geo::DependencyProxyManifestRegistry.state_value(:started) }
        last_synced_at { 1.day.ago }
        retry_count { 0 }
      end
  
      trait :verification_succeeded do
        verification_checksum { 'e079a831cab27bcda7d81cd9b48296d0c3dd92ef' }
        verification_state { Geo::DependencyProxyManifestRegistry.verification_state_value(:verification_succeeded) }
        verified_at { 5.days.ago }
      end
    end
  end

• Create ee/spec/models/geo/dependency_proxy_manifest_registry_spec.rb:

  # frozen_string_literal: true
  
  require 'spec_helper'
  
  RSpec.describe Geo::DependencyProxyManifestRegistry, :geo, type: :model do
    let_it_be(:registry) { create(:geo_dependency_proxy_manifest_registry) }
  
    specify 'factory is valid' do
      expect(registry).to be_valid
    end
  
    include_examples 'a Geo framework registry'
    include_examples 'a Geo verifiable registry'
  end

• Add the following to spec/factories/dependency_proxy_manifests.rb:

  trait :verification_succeeded do
    with_file
    verification_checksum { 'abc' }
    verification_state { DependencyProxyManifest.verification_state_value(:verification_succeeded) }
  end
  
  trait :verification_failed do
    with_file
    verification_failure { 'Could not calculate the checksum' }
    verification_state { DependencyProxyManifest.verification_state_value(:verification_failed) }
  end

• Make sure the factory also allows setting a project attribute. If the model does not have a direct relation to a project, you can use a transient attribute. Check out spec/factories/merge_request_diffs.rb for an example.

• Following the example of Merge Request Diffs add a Geo::DependencyProxyManifestState model in ee/app/models/ee/geo/dependency_proxy_manifest_state.rb:

  # frozen_string_literal: true
  
  module Geo
    class DependencyProxyManifestState < ApplicationRecord
      include EachBatch
      include ::Geo::VerificationStateDefinition
  
      self.primary_key = :dependency_proxy_manifest_id
  
      belongs_to :dependency_proxy_manifest, inverse_of: :dependency_proxy_manifest_state
  
      validates :verification_failure, length: { maximum: 255 }
      validates :verification_state, :dependency_proxy_manifest, presence: true
    end
  end

• Add a factory for dependency_proxy_manifest_state, in ee/spec/factories/geo/dependency_proxy_manifest_states.rb:

  # frozen_string_literal: true
  
  FactoryBot.define do
    factory :geo_dependency_proxy_manifest_state, class: 'Geo::DependencyProxyManifestState' do
      dependency_proxy_manifest
  
      trait :checksummed do
        verification_checksum { 'abc' }
      end
  
      trait :checksum_failure do
        verification_failure { 'Could not calculate the checksum' }
      end
    end
  end

Step 2. Implement metrics gathering

Metrics are gathered by Geo::MetricsUpdateWorker, persisted in GeoNodeStatus for display in the UI, and sent to Prometheus:

• Add the following fields to Geo Node Status example responses in doc/api/geo_nodes.md:
  • dependency_proxy_manifests_count
  • dependency_proxy_manifests_checksum_total_count
  • dependency_proxy_manifests_checksummed_count
  • dependency_proxy_manifests_checksum_failed_count
  • dependency_proxy_manifests_synced_count
  • dependency_proxy_manifests_failed_count
  • dependency_proxy_manifests_registry_count
  • dependency_proxy_manifests_verification_total_count
  • dependency_proxy_manifests_verified_count
  • dependency_proxy_manifests_verification_failed_count
  • dependency_proxy_manifests_synced_in_percentage
  • dependency_proxy_manifests_verified_in_percentage
• Add the same fields to GET /geo_nodes/status example response in ee/spec/fixtures/api/schemas/public_api/v4/geo_node_status.json.
• Add the following fields to the Sidekiq metrics table in doc/administration/monitoring/prometheus/gitlab_metrics.md:
  • geo_dependency_proxy_manifests
  • geo_dependency_proxy_manifests_checksum_total
  • geo_dependency_proxy_manifests_checksummed
  • geo_dependency_proxy_manifests_checksum_failed
  • geo_dependency_proxy_manifests_synced
  • geo_dependency_proxy_manifests_failed
  • geo_dependency_proxy_manifests_registry
  • geo_dependency_proxy_manifests_verification_total
  • geo_dependency_proxy_manifests_verified
  • geo_dependency_proxy_manifests_verification_failed

Dependency Proxy Manifest replication and verification metrics should now be available in the API, the Admin > Geo > Nodes view, and Prometheus.

Step 3. Implement the GraphQL API

The GraphQL API is used by Admin > Geo > Replication Details views, and is directly queryable by administrators.

• Add a new field to GeoNodeType in ee/app/graphql/types/geo/geo_node_type.rb:

  field :dependency_proxy_manifest_registries, ::Types::Geo::DependencyProxyManifestRegistryType.connection_type,
        null: true,
        resolver: ::Resolvers::Geo::DependencyProxyManifestRegistriesResolver,
        description: 'Find Dependency Proxy Manifest registries on this Geo node. '\
                     'Ignored if `geo_dependency_proxy_manifest_replication` feature flag is disabled.',
        alpha: { milestone: '15.5' } # Update the milestone

• Add the new dependency_proxy_manifest_registries field name to the expected_fields array in ee/spec/graphql/types/geo/geo_node_type_spec.rb.

• Create ee/app/graphql/resolvers/geo/dependency_proxy_manifest_registries_resolver.rb:

  # frozen_string_literal: true
  
  module Resolvers
    module Geo
      class DependencyProxyManifestRegistriesResolver < BaseResolver
        type ::Types::Geo::GeoNodeType.connection_type, null: true
  
        include RegistriesResolver
      end
    end
  end

• Create ee/spec/graphql/resolvers/geo/dependency_proxy_manifest_registries_resolver_spec.rb:

  # frozen_string_literal: true
  
  require 'spec_helper'
  
  RSpec.describe Resolvers::Geo::DependencyProxyManifestRegistriesResolver do
    it_behaves_like 'a Geo registries resolver', :geo_dependency_proxy_manifest_registry
  end

• Create ee/app/finders/geo/dependency_proxy_manifest_registry_finder.rb:

  # frozen_string_literal: true
  
  module Geo
    class DependencyProxyManifestRegistryFinder
      include FrameworkRegistryFinder
    end
  end

• Create ee/spec/finders/geo/dependency_proxy_manifest_registry_finder_spec.rb:

  # frozen_string_literal: true
  
  require 'spec_helper'
  
  RSpec.describe Geo::DependencyProxyManifestRegistryFinder do
    it_behaves_like 'a framework registry finder', :geo_dependency_proxy_manifest_registry
  end

• Create ee/app/graphql/types/geo/dependency_proxy_manifest_registry_type.rb:

  # frozen_string_literal: true
  
  module Types
    module Geo
      # rubocop:disable Graphql/AuthorizeTypes because it is included
      class DependencyProxyManifestRegistryType < BaseObject
        graphql_name 'DependencyProxyManifestRegistry'
  
        include ::Types::Geo::RegistryType
  
        description 'Represents the Geo replication and verification state of a dependency_proxy_manifest'
  
        field :dependency_proxy_manifest_id, GraphQL::Types::ID, null: false, description: 'ID of the Dependency Proxy Manifest.'
      end
      # rubocop:enable Graphql/AuthorizeTypes
    end
  end

• Create ee/spec/graphql/types/geo/dependency_proxy_manifest_registry_type_spec.rb:

  # frozen_string_literal: true
  
  require 'spec_helper'
  
  RSpec.describe GitlabSchema.types['DependencyProxyManifestRegistry'] do
    it_behaves_like 'a Geo registry type'
  
    it 'has the expected fields (other than those included in RegistryType)' do
      expected_fields = %i[dependency_proxy_manifest_id]
  
      expect(described_class).to have_graphql_fields(*expected_fields).at_least
    end
  end

• Add integration tests for providing DependencyProxyManifest registry data to the frontend via the GraphQL API, by duplicating and modifying the following shared examples in ee/spec/requests/api/graphql/geo/registries_spec.rb:

  it_behaves_like 'gets registries for', {
    field_name: 'dependencyProxyManifestRegistries',
    registry_class_name: 'DependencyProxyManifestRegistry',
    registry_factory: :geo_dependency_proxy_manifest_registry,
    registry_foreign_key_field_name: 'dependencyProxyManifestId'
  }

• Update the GraphQL reference documentation:

  bundle exec rake gitlab:graphql:compile_docs

Individual Dependency Proxy Manifest replication and verification data should now be available via the GraphQL API.

Step 4. Handle batch destroy

If batch destroy logic is implemented for a replicable, then that logic must be "replicated" by Geo secondaries. The easiest way to do this is use Geo::BatchEventCreateWorker to bulk insert a delete event for each replicable.

For example, if FastDestroyAll is used, then you may be able to use begin_fast_destroy and finalize_fast_destroy hooks, like we did for uploads.

Or if a special service is used to batch delete records and their associated data, then you probably need to hook into that service, like we did for job artifacts.

As illustrated by the above two examples, batch destroy logic cannot be handled automatically by Geo secondaries without restricting the way other teams perform batch destroys. It is up to you to produce Geo::BatchEventCreateWorker attributes before the records are deleted, and then enqueue Geo::BatchEventCreateWorker after the records are deleted.

• Ensure that any batch destroy of this replicable is replicated to secondary sites
• Regardless of implementation details, please verify in specs that when the parent object is removed, the new Geo::Event records are created:

  describe '#destroy' do
    subject { create(:dependency_proxy_manifest) }

    context 'when running in a Geo primary node' do
      let_it_be(:primary) { create(:geo_node, :primary) }
      let_it_be(:secondary) { create(:geo_node) }

      it 'logs an event to the Geo event log when bulk removal is used', :sidekiq_inline do
        stub_current_geo_node(primary)

        expect { subject.project.destroy! }.to change(Geo::Event.where(replicable_name: :dependency_proxy_manifest, event_name: :deleted), :count).by(1)

        payload = Geo::Event.where(replicable_name: :dependency_proxy_manifest, event_name: :deleted).last.payload

        expect(payload['model_record_id']).to eq(subject.id)
        expect(payload['blob_path']).to eq(subject.relative_path)
        expect(payload['uploader_class']).to eq('DependencyProxyManifestUploader')
      end
    end
  end

Release Geo support of Dependency Proxy Manifests

• In the rollout issue you created when creating the feature flag, modify the Roll Out Steps:

  • Cross out any steps related to testing on production GitLab.com, because Geo is not running on production GitLab.com at the moment.
  • Add a step to Test replication and verification of Dependency Proxy Manifests on a non-GDK-deployment. For example, using GitLab Environment Toolkit.
  • Add a step to Ping the Geo PM and EM to coordinate testing. For example, you might add steps to generate Dependency Proxy Manifests, and then a Geo engineer may take it from there.

• In ee/config/feature_flags/development/geo_dependency_proxy_manifest_replication.yml, set default_enabled: true

• In ee/app/graphql/types/geo/geo_node_type.rb, remove the alpha option for the released type:

  field :dependency_proxy_manifest_registries, ::Types::Geo::DependencyProxyManifestRegistryType.connection_type,
        null: true,
        resolver: ::Resolvers::Geo::DependencyProxyManifestRegistriesResolver,
        description: 'Find Dependency Proxy Manifest registries on this Geo node. '\
                     'Ignored if `geo_dependency_proxy_manifest_replication` feature flag is disabled.',
        alpha: { milestone: '15.5' } # Update the milestone

• Run bundle exec rake gitlab:graphql:compile_docs after the step above to regenerate the GraphQL docs.

• Add a row for Dependency Proxy Manifests to the Data types table in Geo data types support

• Add a row for Dependency Proxy Manifests to the Limitations on replication/verification table in Geo data types support. If the row already exists, then update it to show that Replication and Verification is released in the current version.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.