Morpheus Hub Event/Webhook For New Versions/Releases

Ideas
, ,
1

Headline:
Morpheus Hub Events/Webhooks For New Versions/Releases

Description:
We need support for configurable events/webhooks within Morpheus Hub to generate events when a new Morpheus Application Package (Standard/FIPS), Supplemental Package, and Worker Packages are available across all support versions. We need to be able to login into Morpheus Hub to configure these events/webhooks.

We’re currently relegated to notification emails and/or manual polling.

Example/Use case(s):

  • I login to Morpheus Hub.
  • I configure events/webhooks for my CI/CD platform, Slack, etc in Morpheus Hub.
  • New Morpheus version release triggers an event/webhook to send to my configured endpoint.
2

Naturally, we still prefer the webhook/event-driven approach…

Related, but not exactly event-driven, is an idea/recommendations to adjust the folder structure where downloads reside to include versioning and a latest folder and include (including the hashes)?

https://downloads.morpheusdata.com/files/morpheus-appliance_5.4.15-2_amd64.deb

translates to

Appliance:

https://downloads.morpheusdata.com/files/appliance/5.4.x/latest/morpheus-appliance_5.4.15-2_amd64.deb

Supplemental:

https://downloads.morpheusdata.com/files/supplemental/5.4.x/latest/morpheus-appliance-supplemental_5.4.15-1_all.deb

VDI Gateway/Worker:

https://downloads.morpheusdata.com/files/worker/5.4.x/latest/morpheus-worker_5.4.10-1_amd64.deb

(Conversely, versions first in the path if desired)