Closed ricardoconzatti closed 1 month ago
Hi @ricardoconzatti, is this a duplicate of #472?
Hi @ricardoconzatti, is this a duplicate of #472?
Heey @BerryR-RBA. I think it is similar. By the way, I tried right now in vra provider version 0.8.6 and I had the same issue.
Yup, I'm having the same issue with v0.8.6.
Suggest that you (and anyone else impacted) upvote #472
Duplicate of #472
Code of Conduct
This project has a Code of Conduct that all participants are expected to understand and follow:
vRA Version
8.13
Terraform Version
1.6.4
vRA Terraform Provider Version
0.8.3
Affected Resource(s)
vra_cloud_account_vsphere
Terraform Configuration Files
Expected Behavior
Create a new cloud account and allow provisioning to all existing vSphere datacenters (regions). The region name should be the datacenter name (in my example, it should be "Caverna Cloud 02").
Actual Behavior
The new cloud account was created with no errors, but the vSphere regions were configured by ID (externalRegionId). When I edit the new cloud account and save that without any change, the region name changed from externalRegionId to Name (vSphere datacenter name).
Steps to Reproduce
Just run a terraform apply using the code above and check the column Account / Region in Compute (Assembler > Infrastructure > Resources > Compute).
Screenshots
Debug Output
N/A
Panic Output
N/A
Important Factoids
N/A
References
N/A
Community Note