Open brettcurtis opened 3 years ago
I don't see that happening on my end. I tried the same tf version as yours. Can you please attach the debug log of the API response?
That what you're after? I set the TF_LOG=debug when running the plan. I encrypted using hashicorp public key.
@brettcurtis can you please send the log in plain text, you can redact the project info.
Haha, not really that log is FULL of stuff. Anything specific I can look for and share? Or another way to share the encrypted file. I was just following the notes in the issue template.
I have the same issue.
In my case I am upgrading from terraform 0.13.7 to 1.0.4.
It seems that the previous state file has a metadata block, but we don't have that explicitly in our config.
"node_config": [
{
... snip ...
"metadata": {
"disable-legacy-endpoints": "true"
},
Somehow the switch to 1.0.4 is trying to remove that metadata block from the state. A workaround is probably for us to add this metadata explicitly to our config or perhaps an ignore block.
Any update on this? We are seeing it across several clusters now, not sure what's going on exactly?
@gavinreaney - my issue is slightly different in that I have the metadata block defined in our config since I hit this issue: https://github.com/hashicorp/terraform-provider-google/issues/3230
Also of note, going from 0.13 to any other later release (0.14,.15,1.x) triggers this behavior. I can run the same config on 0.13 and see no changes required, but any other version forces replacement with no changes to the config.
I had the same issue while upgrading from a very old version of the provider to the latest one (currently v3.89.0
).
In your configuration, the value for disable-legacy-endpoints
is type bool
:
metadata = {
"disable-legacy-endpoints" = true
}
I was able to overcome the issue by changing the type to string
:
metadata = {
"disable-legacy-endpoints" = "true"
}
Provider documentation is not very helpful, but I noticed that the referenced issue is being mentioned in this PR where, eventually, I saw this comment about the API expecting a string value. I tried it, it worked, I thought I'd share :)
Interesting, thanks @kirkiris - should help us get by a few snags for sure!
Community Note
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 tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Cluster should not rebuild.
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
3230
b/299312565