Make creation of vsphere_virtual_machine
not dependent on resource_pool_id
#1249
Labels
acknowledged
Status: Issue or Pull Request Acknowledged
area/vm
Area: Virtual Machines
documentation
Type: Documentation
enhancement
Type: Enhancement
Milestone
Description
For many small vSphere installations no resource pool is declared and the default Resources resource pool is used. For multiple servers this becomes a problem because the default for the resource pool is "Resources" on all servers. If this tag is used in Terraform it throws an error since there are multiple names and the names must be unique.
It would be so much simpler to allow for resource_pool_id or host_system_id to be used rather than having to synthetically name the multiple "Resources" as something else. Allowing a vsphere_virtual_machine to not require a resource_pool_id but accept a resource_pool_id or host_system_id and assume that the resource pool is Resources if none is declared. This removes the lines of code to define a virtual machine and makes virtual machine creation much simpler for smaller installations.
Potential Terraform Configuration
current
proposed
Community Note
The text was updated successfully, but these errors were encountered: