Epic Goal

• Provide users a way to enforce certain auto-pruning rules at the org level automatically

Why is this important?

• This allows users to more easily control the content in their registry by setting a default auto-pruning policy at registry level that can be applied to all newly created organizations thereby saving the customer time, effort, and storage and enforce registry-wide rules

Scenarios

1. A superuser can define a registry-auto pruning policy with the selection / methods available supported by Quay's auto-pruning policy model
2. A org admin can modify the auto-pruning policy for an individual org but can only define a tighter specification (e.g. even more aggressive pruning by lowering the maximum age of tags), but not a looser one (less aggressive pruning by increasing the allowed maximum age of tags)
3. An org admin cannot remove an org level auto-pruning policy, if a registry wide one is configured
4. Once the default pruning policy is set, it affects all newly created orgs, not existing orgs
5. Once the default pruning policy is altered, it affects all newly created orgs, not existing orgs

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions::

1. Are users able to set expiration at the repo level today?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>