pub/sub webhook framework #84
Description
One thing I wanted to capture here based on discussions with @mortenmj was an idea regarding making the application more hookable.
There are lots of places where we could easily spawn a background process to push some user defined payload to an endpoint based on a condition. Ideally, we'd empower the entire application to allow you to subscribe to lifecycle events and do things like forward messages, trigger notifcations, launch additional processing, etc.
Subscription, endpoint, msg details, creds and conditions could be passed in via jsonnet configuration file(s).
One use case could be to post back to source control whenever an invocation finishes.
Another could be to forward raw BEP messages on to another service for additional handling