Quay is a part of the Red Hat portfolio of cloud-native products. Ansible is currently lacking any automation content for the Quay product offering.

Proposed Solution

There are two parts to this content needs to cover:

1. Content to support the setup, configuration and overall lifecycle management of a Quay cluster especially in an air-gapped environment.
2. Publishing and managing container in a Quay registry. This may be handled as part of a separate Skopeo content collection. 

More details including use cases need to be worked out with the Quay product engineering team.

Requirements

TBD

User Experience 

This solution should conform to the standard recommended Ansible practices. It should reduce the knowledge and time necessary to automate these use cases by abstracting implementation details and error handling and avoiding programming constructs at the play level with a concise declarative style interface. It should provide user conveniences such as reasonable parameter defaults and support of module defaults. The solution should also integrate with the Ansible Platform controller services such as its integrated credential management.

Documentation

The integrations and functionality described will require new documentation for each piece of content.

Use Cases

TBD