[Feature flag] Cleanup mr_vulnerability_code_flow

What does this MR do and why?

Removing completely because this feature flag is not necessary anymore. This feature was deploy in 17.7 milestone.

[Feature flag] Cleanup mr_vulnerability_code_flow

Changelog: other

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After
Screenshot_2025-01-14_at_11.39.03 Screenshot_2025-01-14_at_11.25.07

How to set up and validate locally

  1. Upload a GitLab Ultimate license
  2. Create an empty project
  3. Go to your locally project and edit with web IDE
  4. Create a new file called: gl-sast-report.json and copy the content from here: gl-sast-report.json
  5. Create a new file .gitlab-ci.yml and pasted this content: gitlab-ci.yml
  6. Create a new folder called app and a new file inside called app.py and pasted this content: app.py
  7. Create a new MR
  8. Go into 'Changes' in your MR and you will see the detected vulnerability using shapes next to the specific rows.
  9. Verify that all content in 'Code flow' tab behaves as expected

Numbered steps to set up and validate the change are strongly suggested.

Related to #504344 (closed)

Merge request reports

Loading