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
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 me too comments, 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.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
Follow-up: actually reading the docs instead of trusting the code some earlier developer wrote...
guest_accelerator {
type ="nvidia-tesla-t4"
count =2# known bug: https://github.com/hashicorp/terraform-provider-google/issues/10415
gpu_partition_size =null
}
works just fine. However, the error message is still wrong. The problem wasn't that optional attributes were missing; the problem was that a list assignment was being used instead of a block. 😆
Community Note
Terraform Version
Terraform v1.7.5
on linux_amd64
Your version of Terraform is out of date! The latest version
is 1.8.2. You can update by downloading from https://www.terraform.io/downloads.html
Affected Resource(s)
google_container_node_pool
Terraform Configuration
Debug Output
N/A
Expected Behavior
Running
terraform plan
should have generated a plan, probably with no changes since I only updated the provider version from 4.30.0 to 5.26.0Actual Behavior
I get this error:
This error happens despite the documentation saying those required attributes are optional:
Steps to reproduce
terraform plan
Important Factoids
The plan also unsurprisingly fails after updating to the current terraform 1.8.2. 😉
References
No response
The text was updated successfully, but these errors were encountered: