Skip to content
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

availability_zone_reference not returning in nutanix_clusters #573

Closed
davemays opened this issue Mar 24, 2023 · 4 comments
Closed

availability_zone_reference not returning in nutanix_clusters #573

davemays opened this issue Mar 24, 2023 · 4 comments

Comments

@davemays
Copy link

Nutanix Cluster Information

2022.9 and 6.6

Terraform Version

Affected Resource(s)

Terraform v1.4.2
on windows_amd64

  • provider registry.terraform.io/nutanix/nutanix v1.8.0
  • nutanix_clusters

Terraform Configuration Files

data "nutanix_clusters" "nutanix_clusters" {}

output "cluster" {
value = data.nutanix_clusters.nutanix_clusters
}

Debug Output

Panic Output

Expected Behavior

It should output "availability_zone_reference" in the output of the value.

Actual Behavior

value is not in the output display.

Steps to Reproduce

terraform plan

Important Factors

  • #0000 <!---Github Issue number --->
@abhimutant
Copy link
Contributor

Hi @davemays , availability_zone_reference is not returned by clusters API.

@davemays
Copy link
Author

It lists it in the API docs. Here https://registry.terraform.io/providers/nutanix/nutanix/latest/docs/data-sources/clusters.

Under Entities:

availability_zone_reference: - The reference to a availability_zone.

@abhimutant
Copy link
Contributor

You can verify the API response using the command: export TF_LOG=TRACE . It seems this field is added extra in API doc.

@abhimutant abhimutant added the 1.9 label May 26, 2023
@abhimutant
Copy link
Contributor

Closing this issue as no response from last 30 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants