-
Notifications
You must be signed in to change notification settings - Fork 606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP Hooks #299
Comments
Open Questions
Purposed SolutionTriggers for HooksApplication Triggers
Hooks for application triggers will be configured in the Bonobo settings. Repository Triggers
Hooks for repository triggers can be configured on a per repository basis and globally as part of the Bonobo settings. Whether the global hooks are triggered for a specific repository can be configured in each repository's settings. WebhooksMultiple webhooks can be configured for each trigger. The user can
Webhook FormattersWhen a webhook is configured the user will be able to choose from a list of available formatter implementations. This is to ensure maximum compatibility with other services, because we can't expect them to support a Bonobo specific request format. Initial implementations will be:
|
GitHub's secret setting allows the sending server to sign the payload data in the webhook request so that the receiving server can verify the legitimacy of the Git server and the request. Beacause I generally like to have some form of authenticity for the hook requests and because this seems to be a better solution than using http basic auth, I'll make the GitHub and Bonobo formatter support this. |
GitHub type HTTP hooks for integrations.
The text was updated successfully, but these errors were encountered: