Development registry must be private
What does this MR do and why?
Document the requirement for Secure analyzer development projects to make the container registry private.
This eliminates the risk of users inadvertently pulling an unsanctioned image from the development registry.
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
Numbered steps to set up and validate the change are strongly suggested.
Edited by Thiago Figueiró