Epic Goal

• Implement the new UI as the default UI for Quay

Why is this important?

• The new UI has additional functionality and security enhancements over and above what the current UI has
• It's time to start redirecting quay.io traffic to c.rh
• The current UI will be deprecated and removed in the near future

Scenarios

1. When any user accesses the Quay UI, they are presented with by default the new UI with the new UI toggle set to enabled
2. A user can toggle back to the old UI

Acceptance Criteria

• Tests are updated to account for the new scenarios
• Docs has been notified of this new default behavior and that the old UI will be fully removed at the end of the year in the 3.13 release.

Dependencies (internal and external)

1. TBD

Previous Work (Optional):

1. N/A

Open questions::

1. TBD

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>