github-events: Add WEBHOOK_ID and REQUESTED_ONLY_WEBHOOK_ID filters #689
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an option to only listen to check_run only webhook events for specific webhooks.
In our current deployment, we have multiple webhooks that funnel into the trampoline from multiple sources. Some are repo-level webhooks, some are org-level webhooks. We want to move to a model where we route all of these through a GitHub App, but to do this without downtime or sending duplicate events is tricky. This aims to solve this by restricting a specific webhook to only events that are unique to GitHub Apps - requested check_{run,suite} events.
This will allow us to rollout the new webhook but only pass through these specific events. Once we verify they work, then we can ignore the old webhooks and fully trust the new webhook all in one deployment.
If there are any problems, we can safely rollback the release since the configs are contained here.