Feature Request: self-registration of webhooks / webhook api

[silarsis]

So, I have two use cases for this:

1. I have a desktop app I'd like to write, that will register to watch for builds on certain projects and announce (via audio) success and failure. Because it'll run on a desktop, I figure on using ngrok to setup a local web server and proxy it to a reachable address, then register it against buildkite to receive notifications rather than continually polling. ccmenu isn't quite what I'm after because it's polling and may miss small/fast builds etc.

2. We have a hubot (called hal) in slack that handles our deployments - think hal prod deploy www to deploy our main web server. Hal triggers a build in buildkite to do the deploy, then polls until the build finishes to report back that it's done. Because hal runs in a docker container on a couple of autoscaled clusters, and may run in all sorts of places as we try different infrastructure etc, it would be nice if he could self-register his IP to receive webhooks so he can decide what to report upstream to slack.

We've got a small enough number of builds (although fairly steady/continuous activity) that I don't mind if we're receiving webhooks for all projects rather than for specific projects - and we have no internal security requirements that would mean we have to worry about over-provision of information. So I don't mind if, in both cases, it's just "register to receive all the things" rather than something more targetted.

[arikkfir]

Programmatic registration of BuildKite webhooks would be great for us too. :+1:

[tduffield]

I'd throw programmatic registration of all notifications would be fantastic. For me, Slack would be great!