-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect ResourceType
for NSX Edge
#214
Comments
Issue seems to be from the following terraform-provider-vcf/internal/credentials/constants.go Lines 9 to 24 in b2f7851
|
ResourceType
for NSX Edge
ResourceType
for NSX EdgeResourceType
for NSX Edge
@tenthirtyam, you were faster than me to create the PR. |
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. |
Code of Conduct
Terraform
v.1.9.4
Terraform Provider
v0.10.0
VMware Cloud Foundation
v5
Description
When using resource type NSX_Edge to rotate NSX Edge credentials. It can't find any NSX edge credentials although the API calls can retrieve NSX Edge system credentials. I have identified the issue: The provider requests
resourceType: NSX_EDGE
but API response suggest that the rightresourceType: NSXT_EDGE
.Affected Resources or Data Sources
r/credentials
Terraform Configuration
https://gist.github.com/insidepacket/b549c31c581b4f9f70cda66750039dc1
Debug Output
https://gist.github.com/insidepacket/b549c31c581b4f9f70cda66750039dc1
Panic Output
No response
Expected Behavior
Can get the NSX Edge system credentials and rotate it.
Actual Behavior
Unable to find any NSX Edge system credentials.
Steps to Reproduce
Step 1: stand up a VCF instance or have an existing instance.
Step 2: create the TF template
Step 3:
terraform apply
orterraform plan
.Environment Details
No response
Screenshots
No response
References
No response
The text was updated successfully, but these errors were encountered: