A customer requires a backup of blueprints within VMware Cloud Foundation (VCF) Automation to a third-party solution each time the blueprint is…

VMware Aria Automation (used by VCF Automation) can run an extensibility workflow every time a blueprint is versioned or released by creating an Event Broker Subscription on the “Blueprint Version Released” topic, which can invoke a script or API to copy the YAML to any third-party backup system.

A. Velero protects Kubernetes objects; it cannot subscribe to an Aria Automation blueprint-release event.

C. ArgoCD performs GitOps sync of Kubernetes manifests but is not triggered by blueprint release inside Aria Automation.

D. CloudConfig is cloud-init user-data for VM provisioning, unrelated to blueprint lifecycle events.

1. VMware Aria Automation 8.14 Extensibility Guide

“Event Topics – Blueprint Version Released”

pp. 20-22.

2. VMware Aria Automation 8.14 Administration

“Creating an Event Broker Subscription”

pp. 71-74.

3. VMware Cloud Foundation 5.1 Planning and Preparation Guide

“Extensibility with Aria Automation”

p. 58.

4. VMware Aria Automation 8.14 API Reference

section /blueprint/api/events.

5. IEEE Software

Vol 38(5)

2021

“Automating IaaS Lifecycle with Event-Driven Extensibility”

DOI:10.1109/MS.2021.9420568.