provider/vSphere: VM resource vs. virtual_disk resource - Thick Eager Zeroed disk naming convention about terraform-provider-vsphere HOT 1 CLOSED

This is a dated issue, but just some clarification around this: Unfortunately, this is due to API differences in the different methods that make up virtual disks. The underlying specs - VirtualDiskSpec for the vsphere_virtual_disk resource, and VirtualDiskFlatVer2BackingInfo for vsphere_virtual_machine take different parameters for these options. We try to strike a compromise between API and readability/consistency, but sometimes this is not necessarily possible nor practical.

At this point in time I don't necessarily see a reason to change this interface, as when externally attaching disks you cannot set these options in the VM resource anyway, so the options from vsphere_virtual_disk would take precedence. For further clarification on what the specific thin_provisioned and eagerly_scrub settings mean for each specific disk mode, check out the relevant section in the vsphere_virtual_machine resource documentation.

Thanks!

from terraform-provider-vsphere.