Remove group_level_compliance_dashboard feature flag
What
Remove the :group_level_compliance_dashboard
feature flag
This feature flag exists in the codebase despite having been default-on for quite some time. I've decided to use the Feature Flag Roll Out
template to make sure that the flag is removed completed from all environments correctly but it's likely that some steps can be skipped altogether.
Owners
- Team: groupcompliance
- Most appropriate slack channel to reach out to:
#g_manage_compliance
- Best individual to reach out to: @mattgonzales or @mwoolf
Expectations
What are we expecting to happen?
- Removal of all uses of the flag within the codebase.
- Nothing. This feature is already available in production for 100% of licensed users.
What might happen if this goes wrong?
- Access to the group level compliance dashboard could be broken.
Roll Out Steps
-
Confirm that QA tests pass with the feature flag enabled (if you're unsure how, contact the relevant stable counterpart in the Quality department) -
Enable on staging ( /chatops run feature set feature_name true --staging
) -
Test on staging -
Ensure that documentation has been updated -
Enable on GitLab.com for individual groups/projects listed above and verify behaviour ( /chatops run feature set --project=gitlab-org/gitlab feature_name true
) -
Coordinate a time to enable the flag with the SRE oncall and release managers - In
#production
mention@sre-oncall
and@release-managers
. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
- In
-
Announce on the issue an estimated time this will be enabled on GitLab.com -
Enable on GitLab.com by running chatops command in #production
(/chatops run feature set feature_name 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 -
Remove feature flag and add changelog entry -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel