[Feature flag] Rollout of `periodic_project_authorization_update_via_replica` & `delayed_consistency_for_user_refresh_over_range_worker`
Feature
periodic_project_authorization_update_via_replica
was introduced with !58752 (merged)
delayed_consistency_for_user_refresh_over_range_worker
was introduced with !61883 (merged)
Rollout progress
-
periodic_project_authorization_update_via_replica
: Completed with gitlab-com/gl-infra/production#4779 (closed) on June 3rd -
delayed_consistency_for_user_refresh_over_range_worker
: Completed with gitlab-com/gl-infra/production#4676 (closed)
Owners
- Team: Manage::Access
- Most appropriate slack channel to reach out to:
#g_manage_access
- Best individual to reach out to: Manoj M J
- PM: Melissa Ushakov
Stakeholders
- The Database team
The Rollout Plan
-
Partial Rollout on GitLab.com with beta groups -
Rollout on GitLab.com for a certain period (How long) -
Percentage Rollout on GitLab.com - XX% If it is possible to perform an incremental rollout, this should be preferred. Proposed increments are: 10%
,50%
,100%
. Proposed minimum time between increments is 15 minutes. -
Rollout Feature for everyone as soon as it's ready
Beta Groups/Projects:
-
gitlab-org/gitlab
project -
gitlab-org
/gitlab-com
groups - ...
Expectations
What are we expecting to happen?
What might happen if this goes wrong?
What can we monitor to detect problems with this?
Rollout Timeline
Initial Rollout
Preparation Phase
-
Enable on staging ( /chatops run feature set feature_name true --staging
) -
Test on staging -
Ensure that documentation has been updated (More info) -
Announce on the issue an estimated time this will be enabled on GitLab.com
Partial Rollout Phase
-
Enable on GitLab.com for individual groups/projects listed above and verify behaviour ( /chatops run feature set --project=gitlab-org/gitlab feature_name true
) -
Verify behaviour (See Beta Groups) and add details with screenshots as a comment on this issue
Global Availability (More Info) (Please Note that Beta,Alpha and General Availability (GA) are handled on a product level and not the feature-flag)
-
Coordinate a time to enable the flag with #production
and#g_delivery
on slack. -
Announce on the issue an estimated time this will be enabled on GitLab.com -
Make the feature flag enabled by default i.e. Change default_enabled
totrue
-
Enable on GitLab.com by running chatops command in #production
(/chatops run feature set feature_name true
) -
Announce on the issue that the flag has been enabled -
Cross post chatops slack command to #support_gitlab-com
(more guidance when this is necessary in the dev docs) and in your team channel
Cleanup
This is an important phase, that should be either done in the next Milestone or as soon as possible. For the cleanup phase, please follow our documentation on how to clean up the feature flag.
-
Announce on the issue that the flag has been enabled -
Remove :feature_name
feature flag-
Remove all references to the feature flag from the codebase -
Remove the YAML definitions for the feature from the repository -
Create a Changelog Entry
-
-
Clean up the feature flag from all environments by running this chatops command in #production
channel/chatops run feature delete some_feature
.
Final Step
-
Close this rollout issue for the feature flag after the feature flag is removed from the codebase.
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set --project=gitlab-org/gitlab feature_name false