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 the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.
The terraform plan should result in no changes detected.
Actual Behavior
The below is what is produced by the terraform plan, as can be seen the id, node_config.0.metadata.%, node_config.0.metadata.disable-legacy-endpoints are forcing the recreation of the resource. The metadata objects were never declared, as can be seen above; and, the id shouldn't be new as far as I can tell.
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Apr 18, 2019
Community Note
Terraform Version
Terraform v0.11.13
provider.google v2.1.0
Affected Resource(s)
google_container_cluster
google_container_node_pool
Terraform Configuration Files
Expected Behavior
The
terraform plan
should result in no changes detected.Actual Behavior
The below is what is produced by the
terraform plan
, as can be seen theid
,node_config.0.metadata.%
,node_config.0.metadata.disable-legacy-endpoints
are forcing the recreation of the resource. Themetadata
objects were never declared, as can be seen above; and, theid
shouldn't be new as far as I can tell.Steps to Reproduce
terraform plan
The text was updated successfully, but these errors were encountered: