Add container scanning for registry banner
What does this MR do and why?
Add container scanning for registry banner
- Add to vulnerability report page
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
In rails console:
Feature.enable(:container_scanning_for_registry)
- Import the https://gitlab.com/gitlab-examples/security/security-reports project or any project that generates vulnerabilities
- Run pipeline, generate vulnerabilities
- Navigate to the Vulnerability Report page
- Click on
container registry vulnerabilties
tab - Observe empty state
- Navigate to the security configuration page
- Toggle ON
Container Scanning For Registry
- Navigate to the Vulnerability Report page
- click on
container registry vulnerabilties
tab - Observe alert banner, refresh page confirm it persists
- Dismiss banner, refresh page, confirm banner is gone
- Table OK to render empty since the demo project doesn't currently generate vulns, that has been tested seperately in prior MRs
Numbered steps to set up and validate the change are strongly suggested.
Related to #444883 (closed)
Edited by Fernando Cardenas