Feature Flag Roll Out: feature_flags_legacy_read_only
What
Roll out and then remove the :feature_flags_legacy_read_only
feature flag.
Also remove the :feature_flags_legacy_read_only_override
feature flag, since this is meant to be used to override the :feature_flags_legacy_read_only
flag.
Issue: #220228 (closed)
Owners
- Team: ~"group::progressive delivery"
- Most appropriate slack channel to reach out to:
#g_progressive-delivery
- Best individual to reach out to: @jagood
Expectations
Legacy feature flags will become read-only on gitlab.com
.
What are we expecting to happen?
Legacy feature flags will be read-only via the UI. Users will see a notification in the UI that legacy feature flags are read only, will be removed in GitLab 14.0, and should be migrated by creating new feature flags.
Feature flags will still be mutable via the API.
What might happen if this goes wrong?
What can we monitor to detect problems with this?
Beta groups/projects
If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.
-
gitlab-org/customers-gitlab-com
project
Roll Out Steps
-
Enable on staging -
Test on staging -
Ensure that documentation has been updated -
Enable on GitLab.com for individual groups/projects listed above and verify behaviour - [-] 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 -
Enable on GitLab.com by running chatops command in #production
-
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 -
Enable feature flag by default to roll out to self-managed -
Remove feature flag -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel