Customer Problem:

As a Quay administrator I am overwhelmed by the sheer amount of configuration options and tunables. For some major product features like builders I need to manually discover and understand the config bundle options and manually put them in place There is no quick feedback or validation and I have to view the debug logs of the product to verify something is configured correctly.

Goal: Config editor has large coverage / almost parity with all supported Quay configuration options.

Why is this important: The canonical source of truth for the Quay configuration is the config.yaml / bundle that is supplied to Quay instances. However the preferred way for users to reason about and make changes to the Quay configuration is the config-editor tool. This tool only has partial coverage of what is possible to be specified in the config.yaml.

Expected deliverables:

• configuration option coverage is increased >90%
• configuration validation is attempted whenever possible with reasonable effort