Convert temporary constant to permament
What does this MR do and why?
Describe in detail what your merge request does and why.
Convert temporary constant to permament
- remove todo
- update constant to be permament
- from #365579 (comment 1130451622),
I no longer think creating an API to pass up the supported scanners is the right path forward for a couple of reasons:
- this list would be used for the dropdown in rule mode, but by design, rule mode does not support everything yaml mode allows (e.g. cron). if the backend adds a new feature, we should not assume that rule mode will inherently support it, which is what we would be doing with this list of scanners
- the list of supported scanners is already in the official schema, which is already retrieved by the frontend, so we could probably reuse that
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
 |
No visual change |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Upload a GitLab Ultimate license
- Navigate to a project => Security & Compliance => Policies => New policy => Scan execution
- Mess with the actions builder
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 #365579 (closed)