Change terminology of "configure" to "enable" scanners
Problem to solve
Currently we call enabling scanners (SAST, DAST, etc) "configuring" them. I'd like to start a conversation and consider changing this in the UI and the documentation to the word "enable". Later this year, Static Analysis will be looking at enabling configuration of SAST and Secret Detection in the UI. When that happens, we’ll need more of a differentiation between SAST has been enabled
and SAST has been configured
.
For the time being, users have to manually configure their scanners by adding the .yml file (unless they have Auto DevOps in which case it's added automatically), so this word has not been inaccurate, but this won't be true for long as soon as #34771 (closed) solves for enabling them in the UI.
More info
We'll have to further consider how we communicate in the UI which state each scanner is in:
- Scanners are not setup
- Scanners are enabled by Autodevops (hidden ci yml)
- Scanners are enabled with Default Configuration (ci yml file)
- Scanners are enabled with Custom Configuration
-
Paused
orDisabled
(possibly)
Solution
Replace the following mentioning of the word "configure" to "enable" to mean turning on the scanner type.