[Feature flag] Rollout of `admin-approval-for-new-user-signups`
What
Remove the :admin_approval_for_new_user_signups
feature flag ...
Added with: !43827 (merged)
Enabled by default with : !45233 (merged)
Can be removed from the codebase completely if everything works as expected by 13.6
Owners
- Team: group::access
- Most appropriate slack channel to reach out to:
#g_manage_access
- Best individual to reach out to: Manoj M J
Expectations
This flag is only intended as a means to split the feature &4491 across multiple MRs and we are hopeful of removing this in 13.5 itself.
This feature flag is not intended to be long lived or presented to customers.
What are we expecting to happen?
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/gitlab
project -
gitlab-org
/gitlab-com
groups - ...
Roll Out Steps
-
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 #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
(/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
Edited by Manoj M J