Closed brizzbuzz closed 1 year ago
Alright, i made a bit of progress... it turns out, if you do not assign webhook permissions to the github app, this will cause this loop. IMO this should be an error, or at least a warning.
Now I'm failing due to my private key not being in the correct format... which... not sure how but will carry on 🫡
Alright, i made a bit of progress... it turns out, if you do not assign webhook permissions to the github app, this will cause this loop. IMO this should be an error, or at least a warning.
Now I'm failing due to my private key not being in the correct format... which... not sure how but will carry on 🫡
hmmmm... if we didn't throw an error, we should fix it.
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug Hi, this could very well be an error in my setup, but, if it is, it would still be nice to get some better logging in place.
I have an event source set up to use a github app that I have configured w/ repository read access across my entire organization.
Everything looks ok, except that I can see in the debug of my github app, that any webhook request 503s. My networking config looks correct, and diving down to the pod backing the service that the event source creates, I can see that there are just a loop of the same few logs (despite pod status being healthy).
So, I am imagining that this is to blame for the service being unreachable, but, since there is not any actual error, I am unsure of how to proceed. Any advice here would be greatly appreciated 🙏
To Reproduce Steps to reproduce the behavior:
Unsure
Expected behavior Event source should not 503 when request is received.
Screenshots N/A
Environment (please complete the following information):
Additional context N/A
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.