Draft: Protected containers: Push protection for admin users
requested to merge gitlab-community/gitlab:427546-gerardo-navarro-protected-containers-write-protection-for-container-repositories-integration-container-registry-auth-service-follow-up-bugfix-user-role-admin into master
-
Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA
What does this MR do and why?
- Consider admin mode and admin user when pushing an npm package.
- Currently, the admin user is not able to push a package that is protected by a package protection rule.
- IMPORTANT: This bug issue needs to be resolved before we can really test this MR.
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.
MR Checklist (@gerardo-navarro)
-
Changelog entry added, if necessary -
Documentation created/updated via this MR -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the javascript style guides -
Conforms to the database guides
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.
Related to #427546
Edited by Gerardo Navarro