When adding a cloud account, the region is labeled as the externalRegionId rather than the vSphere datacenter name

[ricardoconzatti]

Code of Conduct

This project has a Code of Conduct that all participants are expected to understand and follow:

• I have read and agree to the project's Code of Conduct

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

data "vra_region_enumeration_vsphere" "this" {
  hostname                            = "vcenter-02.caverna.local"
  username                            = "[email protected]"
  password                            = ""
  accept_self_signed_cert  = true
}

resource "vra_cloud_account_vsphere" "this" {
  name            = "Caverna vCenter 02"
  description  = ""
  hostname    = "vcenter-02.caverna.local"
  username    = "[email protected]"
  password    = ""
  
  regions                                = data.vra_region_enumeration_vsphere.this.regions
  accept_self_signed_cert  = true
}

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

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[BerryR-RBA]

Hi @ricardoconzatti, is this a duplicate of #472?

[ricardoconzatti]

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.

[BerryR-RBA]

Yup, I'm having the same issue with v0.8.6.

Suggest that you (and anyone else impacted) upvote #472

[tenthirtyam]

Duplicate of #472