--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/hashicorp/terraform/issues
IRC: #terraform-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Terraform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to terraform-too...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/CAH5CuEamo1R-rKiJatk8%3DbcciSGC4ExWCEEDsOHKqWEQLGCx-A%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/CAEOVwiP_Fwe3uKkK3kfonnAaKAhj2JM7MhQf9hOiNKr7Fv1iTw%40mail.gmail.com.
Steve,
Another way is to Try setting a debug in your providers.tf and you will get the exact api calls terraform is trying to make to vmware/vsphere.
The debug will produce a .govmomi in your home dir, and underneath there - you will see the logs of the SOAP/API calls terraform is making.
you will see where the permissions are as well.
Side Note in Vsphere - get with your IT team who ever manages the access to your Vmware environment to create a service user account with no membership in any group. Then assign that user "Administrator" role on the Resource pool ONLY you are working on.
for example.
provider "vsphere" {
version = "~> 1.16"
vsphere_server = var.vsphere_vcenter
user = var.vsphere_user
password = var.vsphere_password
allow_unverified_ssl = var.vsphere_unverified_ssl
client_debug = true
}
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/CAH5CuEYN-U-3E_EQznxFDrxnuQxKqrG7jv5uTDKdvAGB2CexTA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/CAEnfFWJ_Z3CPVw4VCiGdkAq9zx2ctn9rNepuU2V5WKBdum1Q4A%40mail.gmail.com.