[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 |
|---|---|
![]() |
![]() |
How to set up and validate locally
- Upload a GitLab Ultimate license
- Create an empty project
- Go to your locally project and edit with web IDE
- Create a new file called:
gl-sast-report.jsonand copy the content from here: gl-sast-report.json - Create a new file
.gitlab-ci.ymland pasted this content: gitlab-ci.yml - Create a new folder called
appand a new file inside calledapp.pyand pasted this content: app.py - Create a new MR
- Go into 'Changes' in your MR and you will see the detected vulnerability using shapes next to the specific rows.
- 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)

