You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the vsphere provider does not account for the vsphere concept of vm folder, and thus, all machines are created at the root level.
Attempts to include path information in the name (similarly to how the template is described) results in vms created at the root level with slashes in the name.
This is occurring on esxi 5.5, terraform 0.6.6
On a side note, it appears that the alternate provider from mkuzmin/terraform-vsphere seems to account for this concept as a separate parameter using the same govmomi library.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems that the vsphere provider does not account for the vsphere concept of vm folder, and thus, all machines are created at the root level.
Attempts to include path information in the name (similarly to how the template is described) results in vms created at the root level with slashes in the name.
This is occurring on esxi 5.5, terraform 0.6.6
On a side note, it appears that the alternate provider from mkuzmin/terraform-vsphere seems to account for this concept as a separate parameter using the same govmomi library.
The text was updated successfully, but these errors were encountered: