This bug is the discussion for the WebHooks design. **Design requirements:** * Don't leak information about security bugs * Leverage existing infrastructure for notifications * Keep it simple Remember that a WebHook is a URL which an application will POST to on a given event. A user should be able to set a WebHook URL for a change to a bug or a bug list. In order to address security concerns, the payload sent to the WebHook's endpoint should be the bug id(s), and the consumer will be responsible for fetching the change. **Scope questions:** * Can a user set a WebHook for a product or component so they are notified about new bugs? * Can a user set up a WebHook through an API (this would be useful for many of our client applications)
Bug 1588661 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This bug is the discussion for the WebHooks design. **Design requirements:** * Don't leak information about security bugs * Leverage existing infrastructure for notifications * Keep it simple Remember that a WebHook is a URL which an application will POST to on a given event. A user should be able to set a WebHook URL for a change to a bug or a bug list. In order to address security concerns, the payload sent to the WebHook's endpoint should be the bug id(s), and the consumer will be responsible for fetching the change. **Scope questions:** * Can a user set a WebHook for a product or component so they are notified about new bugs? * Can a user set up a WebHook through an API (this would be useful for many of our client applications?)
This bug is the discussion for the WebHooks design. **Design requirements:** * Don't leak information about security bugs * Leverage existing infrastructure for notifications * Keep it simple Remember that a WebHook is a URL which an application will POST to on a given event. A user should be able to set a WebHook URL for a change to a bug or a bug list. In order to address security concerns, the payload sent to the WebHook's endpoint should be minimal, and the consumer will be responsible for fetching the change. **Scope questions:** * Can a user set a WebHook for a product or component so they are notified about new bugs? * Can a user set up a WebHook through an API (this would be useful for many of our client applications?)