[FF] triage_and_remediation_profile -- Roll out Triage and Remediation preset scan profiles

Summary

Roll out the feature currently behind the triage_and_remediation_profile feature flag.

The flag gates three GitLab-provided "Triage and Remediation" scan profile presets (Conservative, Standard, Proactive) offered as default scan profiles, along with exposing the TRIAGE_AND_REMEDIATION scan type and the ability to create/attach those presets.

• DRI: @gkatz1
• Team Slack channel: #<slack-channel-of-dri-team>

Note

Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. Feature flag controls · Feature flag lifecycle

What could go wrong?

Blast radius is small and read-mostly: the flag controls visibility of GitLab-provided preset scan profiles in the group-level availableSecurityScanProfiles GraphQL query and the ability to create/attach them. Low data-loss risk — the presets themselves are static configuration; attaching a preset persists scan-profile/trigger rows. Watch the general Rails/GraphQL error-rate and latency dashboards on dashboards.gitlab.net.

Rollout

Run all production /chatops in #production and cross-post the results to #<slack-channel-of-dri-team>. Background: incremental rollout process, feature actors.

Non-production

/chatops gitlab run feature set triage_and_remediation_profile 50 --actors --dev --pre --staging --staging-ref
/chatops gitlab run feature set triage_and_remediation_profile true --dev --pre --staging --staging-ref

Production — percentage rollout (wait ≥15 min between steps, watch dashboards):

/chatops gitlab run feature set triage_and_remediation_profile <percentage> --actors

Or target specific actors instead:

/chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss triage_and_remediation_profile true
/chatops gitlab run feature set --group=gitlab-org,gitlab-com triage_and_remediation_profile true
/chatops gitlab run feature set --user=gkatz1 triage_and_remediation_profile true

Before global rollout

Confirm the relevant gotchas before going to 100% — see enabling a feature for GitLab.com:

• Docs + version history updated
• Breaking changes announced, if any
• Change management issue opened, if required
• External API consumers handled with a fail-open mechanism, if applicable

Cleanup

Remove the flag once deemed stable — see cleaning up. Track it here, or open a follow-up Feature Flag Cleanup issue. Remove the flag and its YAML definition from the codebase, then:

/chatops gitlab run release check https://gitlab.com/gitlab-org/gitlab/-/merge_requests/251938 19.4
/chatops gitlab run feature delete triage_and_remediation_profile --dev --pre --staging --staging-ref --production

Rollback

/chatops gitlab run feature set triage_and_remediation_profile false                                         # production
/chatops gitlab run feature set triage_and_remediation_profile false --dev --pre --staging --staging-ref     # non-production
/chatops gitlab run feature delete triage_and_remediation_profile --dev --pre --staging --staging-ref --production  # remove entirely