fix: webhooks getting not found error when triggering workflows #671
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ryan Hopper-Lowe <[email protected]>
ryanhopperlowe
requested review from
thedadams,
njhale,
StrongMonkey and
g-linville
ryanhopperlowe
changed the title
thedadams
approved these changes
Nov 26, 2024
ryanhopperlowe
deleted the
fix/admin/webhooks-not-triggering-workflows
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes the issue where a webhook execution throws a not found error.
This fix solves that by providing the default namespace to the workflow execution handler.
Signed-off-by: Ryan Hopper-Lowe [email protected]