[Feature flag] Rollout of `audit_log_export_csv`

What

Remove the :audit_log_export_csv feature flag introduced by !31191 (merged).

Owners

• Team: groupcompliance
• Most appropriate slack channel to reach out to: #g_manage_compliance
• Best individual to reach out to: Tan Le (@tancnle)

Expectations

What are we expecting to happen?

Administrators can export audit events to CSV via Admin Area > Monitoring > Audit Log.

What might happen if this goes wrong?

Administrators are unable to export, most likely 500 due to timeout.

What can we monitor to detect problems with this?

Monitoring issues reported in gitlab-org/gitlab.

Beta groups/projects

N/A - This is an instance-wide feature.

Roll Out Steps

• Enable on staging (/chatops run feature set audit_log_export_csv 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 audit_log_export_csv true) - this is an instance-wide feature.
• Coordinate a time to enable the flag with the SRE oncall and release managers
  • In #production by pinging @sre-oncall
  • In #g_delivery by pinging @release-managers
• 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 audit_log_export_csv 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

Rollback Steps

• This feature can be disabled by running the following Chatops command:

/chatops run feature set audit_log_export_csv false