Epic Goal

• Give users the option to ignore logging failures completely

Why is this important?

• When external systems (e.g. Splunk, ElasticSearch etc) are configured as audit log destinations it is possible for those systems to be down
• With a way to ignore audit logging failures outages of external logging systems would result in outages of the entire registry platform, which may be undesirable

Scenarios

1. A CI pipeline pushes an image to a Quay instance which has Splunk configured as audit log storage. Pushes normally fail if the Splunk instance is intermittently unavailable. With the new config switch ALLOW_WITHOUT_STRICT_LOGGING set to True the pushes would succeed, which may be desirable since registry uptime outweighs audit log system uptime. The logging event is logged to the stdout instead.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

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>