You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.
There are scenarios where one may want to create and use webhooks from public github.com/repo to a private Kabanero environment. What are the steps to do this?
Enterprise infrastructure owner needs to expose a public IP address / endpoint that the github webhook will connect to when commit events occur. The webhook extension needs to provide a routeable endpoint (alias) to github
RUNTIME
Public Public Private
github.com ---event----=> webhook endpoint
github.com ---event---=> webhook alias --->NAT ---> webhook endpoint
REGISTRATION
Note: not entirely sure about this flow. At a minimum, the pipeline extension will call outbound to github. Maybe there is a handshake which involves a helloworld invocation of the runtime flow? If there were no side effects than it would be sufficient as a workaround to create the webhook on github directly. An additional concern is what if any security implications would there be for allowing such a manual external registration?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are scenarios where one may want to create and use webhooks from public github.com/repo to a private Kabanero environment. What are the steps to do this?
Enterprise infrastructure owner needs to expose a public IP address / endpoint that the github webhook will connect to when commit events occur. The webhook extension needs to provide a routeable endpoint (alias) to github
RUNTIME
Public Public Private
github.com ---event----=> webhook endpoint
github.com ---event---=> webhook alias --->NAT ---> webhook endpoint
REGISTRATION
Note: not entirely sure about this flow. At a minimum, the pipeline extension will call outbound to github. Maybe there is a handshake which involves a helloworld invocation of the runtime flow? If there were no side effects than it would be sufficient as a workaround to create the webhook on github directly. An additional concern is what if any security implications would there be for allowing such a manual external registration?
The text was updated successfully, but these errors were encountered: