Fix webhooks for users with multiple API keys #3151
Merged
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.
The vast majority of the 34,000 failed delayed jobs stored in the database are all exceptions caused by
user.api_key
b 8000 eingnil
. That is in fact the expected and desired state now that usershas_many :api_keys
, so this PR adds tests to make sure there won't be exceptions and then uses the first API key it can find to generate an auth header for the webhook. We should probably use a dedicated webhook secret at some point, but for now this will at least stop the ongoing exceptions.The backtrace that led me here was: