Epic Goal

• Support mirroring of sets of repositories or entire namespaces in a single configuration step so that changes in set of repos to mirrors are automatically discovered and captured

Why is this important?

• repo mirroring is done individually today, per repository
• users often want to mirror various related repositories from a single namespace and/or quay organization

Scenarios

1. As a Quay user I want to mirror an entire Quay organization from the remote Quay deployment to a local Quay deployment
2. As a Quay user I want to configure mirroring a selected set of repositories into my organization from a remote registry in a single step
3. As a Quay user I want to mirror a set of repositories from a remote registry that match a certain regular expression (including "everything")

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Bulk mirroring works with any OCI-compliant remote registry

Open questions::

1. Are there any Quay-specific features / use cases that arise when the remote Registry is also a Quay instance?

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>