[Feature flag] Enable logging git push events by default on gitlab.com
What
Enable the :repository_push_audit_event
feature flag on gitlab.com by default
Owners
- Team: groupcompliance
- Most appropriate slack channel to reach out to: #g_manage_compliance
- Best individual to reach out to: @mattgonzales
Expectations
What are we expecting to happen?
We are expecting a large increase in the number of database writes from enabling this feature flag by default on gitlab.com
What might happen if this goes wrong?
It could cause significant performance degradation issues.
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 -
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 -
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