Epic Goal

• Allow users to create and manage a pull-through cache organization from the UI and distinguish it from regular organizations.

Why is this important?

• Pull-through caching works based on an organization in Quay. Such an organization transparently fetches images from a configured upstream registry or a specific namespace in an upstream registry and serves these images from a cache on subsequent pulls. In the old UI this was a post-creation configuration step for an organization and there was no way to tell from a list of organizations, which one is configured as a pull-through cache.
  In the new UI there is currently no way to create or configure a pull-through cache organization

Scenarios

1. A user is able to use only the new ui to configure pull-thru caching

Acceptance Criteria

• allow the creation of a pull-through cache with a specific configuration wizard in a single flow, instead of after creating a regular organization
• allow to change / remove the pull-through cache configuration of an organization
• visually distinguish a pull-through cache organization in the organization list view

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>