[Feature flag] Rollout of `revoke_managed_users_token`
What
Remove the :revoke_managed_users_token
feature flag once the user facing changes have been implemented in #214811 (closed)
Owners
- Team:
Compliance
- Most appropriate slack channel to reach out to:
#g_manage_compliance
- Best individual to reach out to: Aishwarya Subramanian (@asubramanian1)
Expectations
The FF revoke_managed_users_token
was introduced to backend changes required to allow managed group admins to revoke the personal access tokens of their managed users.
What are we expecting to happen?
What might happen if this goes wrong?
What can we monitor to detect problems with this?
Roll Out Steps
-
Ensure #214811 (closed) is completed -
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, remove revoke_button_available?
and add changelog entry -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel
Edited by Aishwarya Subramanian