Broker for CI/CD

[uniqueg]

For a decoupled CI/CD pipeline strategy for delivering subscription-based automatic updates to participating/interested nodes in the ELIXIR Cloud network that is currently under early development, the service registry could serve as a broker between CI endpoints (container registries) and deployments, via a callback mechanism (set webhook, ideally automatically, from cloud registry upon changes to a specific image type, e.g., prod, dev etc, send callback to service listening at service cluster ) and/or proactive polling for intervals at specified intervals. Specifically, the service registry could manage subscriptions, set webhooks and relay webhooks and make sure entries in the service registry are synchronized with deployments.

Details for this are still under discussion, but ideas and progress could be gathered here en route to a concrete plan for an implementation. A hard requirement for this is probably a thin interface giving developers and especially service administrators as much flexibility/autonomy as possible. In production, it is also paramount to ensure that access to service management and subscription endpoints and the underlying auto-delivery functionality is limited and secure.