[Feature flag] [Geo] Enable MR diffs verification feature

Feature

This feature uses the :geo_merge_request_diff_verification feature flag!

Owners

Stakeholders

The Rollout Plan

  • Rollout Feature for everyone as soon as it's ready

Expectations

What are we expecting to happen?

Nothing is expected to change on GitLab.com since Geo is not used on the site.

On staging, we expect verification to work for new and old MR diffs.

What might happen if this goes wrong?

  • Turn off the feature flag
  • If (unlikely) that is not enough !60935 (merged) can be rolled back
  • On staging, some MR diffs will not be verified, but that is not a regression.

What can we monitor to detect problems with this?

  • Check Sentry errors on staging

Rollout Timeline

Rollout Steps

Preparation Phase

Full Rollout Phase

  • Make the feature flag enabled by default i.e. Change default_enabled to true

  • Cross post chatops slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel

  • Announce on the issue that the flag has been enabled

  • Create a cleanup issue using the "Feature Flag Removal" template

Rollback Steps

  • This feature can be disabled by running the following Chatops command:
/chatops run feature set --project=gitlab-org/gitlab geo_merge_request_diff_verification false
Edited by Aakriti Gupta