[SOLVED] Runboat unable to handle webhook when RUNBOAT_GITHUB_WEBHOOK_SECRET not set #85
23kbps
started this conversation in
Deployment
Replies: 1 comment 3 replies
-
|
Your first stack trace is possibly due to the webhook being configured to post x-www-url-encoded instead of json. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have runboat up and running in an EKS cluster,
RUNBOAT_GITHUB_WEBHOOK_SECRETis not set in env varDocker image is
ghcr.io/sbidoul/runboat:latestIn repo, webhook is not set the secret. When we push commit, runboat throw exception:
If we set the secret in github webhook and put the secret into k8s secret, runboat just throw a warning and nothing happens.
I can confirm that webhook secret and k8s secret is setup correctly.
This is our new build and first time using runboat, any idea that I could do it wrong in any step?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions