Why my Harbor kit for air-gapped VKS checks everything outside, carries one transfer that proves itself, and asks instead of making you edit YAML inside. What changed in 1.4, and what bit me getting there.
The Cisco ACI plugin for vRealize was validated through 8.4 and never caught up to Aria Automation 8.18. Here is the Orchestrator integration that places a VM in an EPG anyway.
Open-source tooling to capture an Aria Automation 8.18 environment as YAML and rebuild it on VCF Automation 9.1, with a placement check that catches API calls returning HTTP 200 and doing nothing.
HPE Synergy SAN-boot blades show zero storage at install. Build a custom ESXi 9.0.2 ISO merging the VMware base depot with the HPE Synergy AddOn via PowerCLI Image Builder.
VMware vSphere 8.0 STIG compliance tooling for federal environments: train-vmware password fix, enhanced InSpec runner with -allhosts, and CKL→CKLB converter for STIG Viewer 3.x.
Two Python inventory generators bridging Aria Automation provisioning to Ansible: vSphere with intelligent IP resolution and HPE OneView 6.6/8.9/10.0 multi-version support.
Replace decades of bolted-on Windows post-deploy PowerShell with 10 idempotent Ansible roles. Desired-state dispatcher, vault-stored secrets, no more 8-minute sleep timers.
Three production vRO JavaScript actions: dynamic Service Broker dropdowns, intelligent network profile routing, and post-provision disk attach. When the blueprint isn’t enough.
A six-month VMware Aria Automation modernization journey: 50+ vRO workflows replaced with one self-service blueprint, BlueCat IPAM, NSX Federation, and 6 open-source repos.
One Aria Automation blueprint. Three OS families. Two datacenters. 26 inputs. The hybrid VLAN/NSX network pattern, count:0 conditional NICs, and dynamic catalog forms.
