Protected containers: Remove field "Minimum access level for delete"

  • 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. As a benefit of being a GitLab Community Contributor, you can request access to GitLab Duo.

What does this MR do and why?

Protected containers: Remove field "Minimum access level for delete"

  • During rollout of the feature "Protected containers", we noticed that the field "Minimum access level for delete" is visible, but the aspect delete protection has not been implemented yet; therefore, the existence / visibility of the field "Minimum access level for delete" might lead to unnecessary confusion.
  • This MR intends to remove the field "Minimum access level for delete" from the frontend as suggested here: #480385 (comment 2193605295)

🛠️ with ❤️ at Siemens

References

Please include cross links to any resources that are relevant to this MR This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

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)

Screenshots or screen recordings

This MR removes the field Minimum access level for delete because the delete protection feature is not implemented yet.

Before After
image image

How to set up and validate locally

  1. Go to the registry settings of a project: http://gdk.test:3000/flightjs/Flight/-/settings/packages_and_registries

Related to #480385 (closed)

Edited by Gerardo Navarro

Merge request reports

Loading