Infrastructure Automation: Enforcing VCF Automation Upgrade Prechecks with Orchestrator

The Cloud Architect


The Cloud Architect
VCF Automation upgrades fail most often for predictable reasons: skipped prechecks, deprecated feature usage, and environment drift.
Source KB: https://knowledge.broadcom.com/external/article/389563/essential-prechecks-for-a-successful-vcf.html
Orchestrator action: upgrade precheck runner
Goal: run the same upgrade readiness checks every time, and produce a machine-readable PASS/FAIL report.
Workflow steps (VMware Aria Orchestrator)
- Create a workflow: 'VCF Automation - Upgrade Precheck Runner'
- Inputs: vcfAutomationEndpoint (string), notifyEmail (string, optional)
- Step 1: Call the VCF Automation precheck API endpoint (or scripted precheck task) and capture results.
- Step 2: Fail immediately if any blocking checks are returned (exit workflow with the failing check names).
- Step 3: On PASS, generate a short report artifact (JSON/text) and optionally email it to the change owner.
Expected outcome
You stop treating upgrades like one-off events. The workflow enforces readiness consistently.


