Serve SAST FP detection flow 1.1.0-dev behind a flag

What does this MR do and why?

Adds a wip feature flag, sast_fp_detection_flow_1_1_0, which is off by default.

When the flag is on for a top-level group (checked on container.root_ancestor), the SAST false positive detection flow runs version 1.1.0-dev instead of 1.0.0. This uses the existing flow_version_resolver hook in ee/app/models/ai/catalog/foundational_flow/sast_fp_detection/definition.rb.

Flow 1.1.0-dev comes from the AI gateway MR. It passes the scanner's identifiers and code flows to the false positive agent, using new dev prompt versions.

We plan to enable it only for the gitlab-org group on gitlab.com to try the new prompts. Nobody else is affected. Do not enable the flag until the AI gateway MR is deployed, or the gateway will not find flow 1.1.0-dev.

How to validate

  • Run /chatops run feature set --group=gitlab-org sast_fp_detection_flow_1_1_0 true.
  • Trigger false positive detection on a SAST vulnerability in a gitlab-org project and check that the workflow's flow version is 1.1.0-dev.
  • Specs are in ee/spec/models/ai/catalog/foundational_flow/sast_fp_detection/definition_spec.rb.

🤖 Generated with Claude Code

Edited by Savas Vedova

Merge request reports

Loading
Loading