Epic Goal

• Allow Quay to support metadata passed via annotations so that OCI types that do not use labels can still pass important information, such as expiration timestamps

Why is this important?

• As Quay moves towards being a general artifact store via OCI v1.1, there will be OCI types that do not use labels to pass metadata. Annotations should be a common denominator and will allow tools such as Cosign to pass expiration information, thereby allowing them to expire alongside images.

Scenarios

1. A user is able to use Cosign to annotate and store an artifact in Quay that can then be parsed by Quay to set expiration date

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. ...

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>