You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Terraform Version 1.0.8 Nutanix terraform provider 1.9.3
Affected Resource(s)
*data "nutanix_subnet" "subnet" your query returned more than one result. Please use subnet_id argument or use additional filter instead
unable to filter subnet by cluster when building a vm and specifying a subnet name. We have the same subnet names configured on several clusters. query returns all matching subnet names in prism central server. Need a clear example of how to filter results further if this is supported by cluster.
when using data sources:
data "nutanix_subnet" "test" {
subnet_id = nutanix_subnet.test.id
}
data "nutanix_subnet" "test-name" {
subnet_name = nutanix_subnet.test.name
}
Terraform Configuration Files
# Copy-paste your Terraform configurations here - for large Terraform configs,# please use a service like Dropbox and share a link to the ZIP file.
Debug Output
Panic Output
References
#0000 <!---Github Issue number --->
The text was updated successfully, but these errors were encountered:
Nutanix Cluster Information
Terraform Version 1.0.8 Nutanix terraform provider 1.9.3
Affected Resource(s)
*data "nutanix_subnet" "subnet" your query returned more than one result. Please use subnet_id argument or use additional filter instead
unable to filter subnet by cluster when building a vm and specifying a subnet name. We have the same subnet names configured on several clusters. query returns all matching subnet names in prism central server. Need a clear example of how to filter results further if this is supported by cluster.
when using data sources:
data "nutanix_subnet" "test" {
subnet_id = nutanix_subnet.test.id
}
data "nutanix_subnet" "test-name" {
subnet_name = nutanix_subnet.test.name
}
Terraform Configuration Files
Debug Output
Panic Output
References
The text was updated successfully, but these errors were encountered: