Move container scanning for registry to new card
What does this MR do and why?
Move container scanning for registry to new card
-
Separate into own card
-
Update status logic
-
Unit tests
-
Update the feature flag name (Forced to do this as part as defining the new feature tier, the feature name and feature flag were the same, so the pipeline started failing, and we were forced to change it in this MR)
Notes for reviewer
- Follow-up to !147968 (merged)
- Feature flag logic in !147968 (merged)
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 (with feature flag on)
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
![]() |
![]() |
![]() |
![]() ![]() |
Screenshot Feature flag off ( no change)
Before | After |
---|---|
![]() |
![]() |
How to set up and validate locally
- On an existing or new project navigate to `http://gdk.test:3000///-/security/configuration
- Or from the nav "Secure -> Security Configuration"
- Run with flag off
- Turn flag on in rails console
Feature.enable(:container_scanning_for_registry_flag)
Related to #460935 (closed)
Edited by Fernando Cardenas