[Feature flag] Enable go implementation of UserRevert
What
Remove the :gitaly_go_user_revert
feature flag implemented in #3072 (closed)
Owners
- Team: Gitaly
- Most appropriate slack channel to reach out to:
#g_gitaly
- Best individual to reach out to: @proglottis
Expectations
What release does this feature occur in first?
Feature flag was released in %13.6.
What are we expecting to happen?
For reverts to continue to behave as before.
What might happen if this goes wrong?
Higher error rate, incorrectly rejected/applied reverts that were triggered by the gitlab UI.
What can we monitor to detect problems with this?
Problems with the gitaly RPC UserRevert
in sentry/logs
Roll Out Steps
-
Read the documentation of feature flags -
Add featureflagstaging to this issue -
Enable on staging -
Test on staging -
Ensure that documentation has been updated -
Announce on the issue an estimated time this will be enabled on GitLab.com -
/chatops run feature set gitaly_go_user_revert 5
-
/chatops run feature set gitaly_go_user_revert 25
-
/chatops run feature set gitaly_go_user_revert 50
-
/chatops run feature set gitaly_go_user_revert 100
-
-
Add featureflagproduction to this issue -
Enable on GitLab.com by running chatops command in #production
-
Cross post chatops slack command to #support_gitlab-com
and in your team channel -
Announce on the issue that the flag has been enabled -
Remove feature flag and add changelog entry -
Close this issue
Edited by James Fargher