Move Security Configuration scanner status strings to frontend
Why are we doing this work
This is about defining the scanner status strings (Enabled
, Not enabled
, Enabled with Auto DevOps
) in the frontend, and removing them from the backend.
The scanner status strings in the Security Configuration page are currently defined in the backend. Since all the data necessary to determine which user-facing strings to render is already provided to the frontend, the frontend should determine what to render. In addition, the DAST Profiles "scanner" must be handled in an awkward way, since it cannot be "enabled" or "disabled" as such.
Instead, the aim here would be to create scanner-specific components for the status, using component polymorphism similar to what's described in #323376 (closed), but for the Status
column rather than the Manage
column.
Relevant links
Non-functional requirements
- [-] Documentation:
- [-] Feature flag:
- [-] Performance:
-
Testing: -
Update component tests for configuration table -
Add new component tests for split out components
-
Implementation plan
-
Extract status_dast_profiles.vue
fromfeature_status.vue
-
Extract status_generic.vue
fromfeature_status.vue
-
Embed above components into scanners
constants definition (seescanners_constants.js
) -
Use dynamic component in configuration_table.vue
to render provided scanner-specific component