Move SAST configuration path to CE
What does this MR do and why?
As SAST became a free feature, we need to move related code to the CE part of the codebase.
This change is related to bigger work of moving Security Configuration Presenter to FOSS
Screenshots or screen recordings
This change doesn't have any user-visible changes
How to set up and validate locally
Go to {hostname/group/project}/-/security/configuration and observe page that is rendered correctly.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #342135 (closed)
Merge request reports
Activity
changed milestone to %14.5
added Category:SAST Category:Vulnerability Management Deliverable Enterprise Edition GitLab Core GitLab Free GitLab Premium GitLab Ultimate backend devopssecure groupcomposition analysis maintenancerefactor missed-deliverable missed:14.4 pipeline:run-as-if-foss quad-planningcomplete-no-action sectionsec typemaintenance workflowin dev + 1 deleted label
assigned to @brytannia
added typefeature label and removed typemaintenance label
requested review from @theoretick
@theoretick could you please review this MR?
removed GitLab Premium label
removed GitLab Ultimate label
removed missed-deliverable label
removed missed:14.4 label
removed Enterprise Edition label
removed Deliverable label
1 Message 
CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the
Changelogtrailer to the commit message you want to add to the changelog.If you want to create a changelog entry for GitLab EE, also add the
EE: truetrailer to your commit message.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend Matt Kasa ( @mattkasa) (UTC-7, 10 hours behind@brytannia)Sean McGivern ( @smcgivern) (UTC+0, 3 hours behind@brytannia)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-reviewjob that generated this comment.Generated by
removed quad-planningcomplete-no-action label
removed typefeature label
added typemaintenance label
Allure report
allure-report-publishergenerated test report for 1254c37f!review-qa-smoke:
@theoretick, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline has been started.
For more info, please refer to the following links:
requested review from @ebaque and removed review request for @theoretick
@brytannia Tested this locally, all good
enabled an automatic merge when the pipeline for 474f1316 succeeds
mentioned in commit a162dd21
added workflowstaging-canary label and removed workflowin dev label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label
