Feature flag rollout issue for DAST Site Profile - Rest API option

What

Remove the :security_dast_site_profiles_api_option feature flag ...

Owners

• Team: groupdynamic analysis
• Most appropriate slack channel to reach out to: f_dast_on_demand_scans
• Best individual to reach out to: @djadmin @philipcunningham

Expectations

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/security-products/dast-site-profile-testing project
• ...

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 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
• 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

Cleanup

Tracked via - #330744 (closed)

Rollback Steps

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

/chatops run feature set --project=gitlab-org/gitlab feature_name false