Providers
vSphere
Not yet scoredConnects via the vSphere Automation API session endpoint, with an optional legacy VI/JSON API gated to vCenter 8.0 Update 1 or later.
Day-2 operations like snapshots or vMotion return an explicit unsupported-API error on older vCenter versions instead of failing in a way that looks like a generic connection problem.
- A minimal-role privilege system (Inventory, Apply-Core, Apply, Apply-Crypto) means day-2 accounts never receive Authorization.* privileges.
- Snapshots, hot reconfiguration, and vMotion all require the newer vCenter API — older versions get an explicit unsupported error rather than a silent failure.
This provider isn't yet included in the capability maturity matrix — it has real Terraform generation and validation, but FinOps, drift, day-2, and copilot support aren't independently rated yet.
A minimal real resource
resource "vsphere_virtual_machine" "web" {
name = "web"
resource_pool_id = data.vsphere_resource_pool.pool.id
num_cpus = 2
memory = 4096
}Under the hood
- backend/src/services/vsphere/vcenter-client.ts
- backend/src/services/vsphere/vsphere-minimal-role-privileges.ts