Note that traditional webhooks (REST based) are exactly what is needed to make Plastic Cloud able to send and receive notifications directly against other cloud-based services without any intermediary.

Websockets are superior in a number of ways, but I believe their primary use will be to connect Plastic Cloud to custom-made software (or custom-made bridging solutions to other cloud or on-prem services).

Websockets and REST-based webhooks solve slightly different use cases. Both are useful.

Hi Brandon,

Thanks for sharing this.

We are working on a bunch of features to support DevOps, and better triggers (and support for Cloud) will be part of it.

What we have in mind is something like what Slack does for bots: you open a websocket to the server (the cloud server in your case) and then register which repos you are interested on, and notifications will come.

We prefer this better than regular webhooks so that people can configure their hooks behind the firewall, no need for public endpoints.

pablo