Instance wide Cleanup policy for tags for the Container Registry

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

Currently you're able to set the Cleanup Policy on the project level. Having a feature to do so for all projects in an instance allows for administrators to enforce such a policy for everyone.

Additionally, being able to enable/disable any/all cleanup policies instance wide would be helpful as well.

Intended users

• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)
• Sidney (Systems Administrator)
• Rachel (Release Manager)

User experience goal

The user should be able to configure the Expiration Policy via the UI (or API) to enforce the policy instance wide. Possibly in <https://instance>/admin/application_settings/ci_cd under Container Registry

Proposal

In addition to being able to configure the policy, an Admin should also be able to turn this feature off for all of their organization's projects.

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references