Epic Goal

• Update pagination so that it is compliant with current and upcoming OCI changes

Why is this important?

• Users expect Quay to be fully OCI compliant, it is table stakes for being a registry

Scenarios

1. Allow the use of the n parameter in the API endpoint /v2/<name>/tags/list?n=<integer>
2. Return a Link header in the response until there are no more tags to paginate through
3. Return a Link header in the response when the amount of requested tags is higher than the configured page size and only return that many entries per page at max
4. The last parameter can be used in combination with the n parameter to paginate through the list of tags as an alternative to following the Link header

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. https://github.com/opencontainers/distribution-spec/blob/main/spec.md
2. https://github.com/opencontainers/distribution-spec/pull/47

Open questions::

1. Are the above scenarios going to change prior to implementation?
2. Should we wait to merge until OCI adoption?

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>