Epic Goal

• Users are able to configure webhooks to use authentication

Why is this important?

• When using the repository notification feature, Quay does not allow users to specify authentication credentials for notification of type webhook POST
• There are certain services, such as GitHub's repository_dispatch event, that require webhook authentication in order to trigger the other actions.

Scenarios

1. A User is able to configure a repository notification webhook with authentication that can be be sent to GitHub to trigger a GitHub Action

Acceptance Criteria

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

Dependencies (internal and external)

1. TBD

Previous Work (Optional):

1. TBD

Open questions::

1. Do we only need to support basic auth?
2.  

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>