[Feature flag] Cleanup geo_project_repository_replication_v2

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Label this issue
  • Close this issue

Summary

This issue is to cleanup the geo_project_repository_replication feature flag, after the feature flag has been enabled by default for an appropriate amount of time in production - we would want the FF around for 2 or 3 milestones, since the users of Geo, usually don't upgrade every milestone. Keeping it around longer, will give us a better chance to see it in production.

Once this FF is removed, we can no longer toggle between projects and project_repositories tables for Geo replication and verification.

This FF was introduced in !194051 (closed)

As part of this cleanup, we need the following:

  • Remove project_id column from project_repository_registry (closed MR here
  • Remove the code that depends on this FF
  • Remove the enumeration of projects entirely, for Geo replication and verification
  • Update documentation added in Geo: Document the 2 versions of project repo re... (#550191) and Geo: Document the difference in number of proje... (#547895)

Owners

  • Team: Geo
  • Most appropriate slack channel to reach out to: #g_geo
  • Best individual to reach out to: Aakriti (@aakriti.gupta )
  • PM: @sranasinghe

Stakeholders

Expectations

What might happen if this goes wrong?

Cleaning up the feature flag

  • Specify in the issue description if this feature will be removed completely or will be productized as part of the Feature Flag cleanup
  • Create a merge request to remove <feature-flag-name> feature flag. Ask for review and merge it.
    • Remove all references to the feature flag from the codebase.
    • Remove the YAML definitions for the feature from the repository.
    • Create a changelog entry.
  • Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post.
    • /chatops run auto_deploy status <merge-commit-of-cleanup-mr>
  • Close the feature issue to indicate the feature will be released in the current milestone.
  • If not already done, clean up the feature flag from all environments by running these chatops command in #production channel: /chatops run feature delete <feature-flag-name> --dev --pre --staging --staging-ref --production
  • Close this rollout issue.
Edited Nov 21, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading