Closed hashibot closed 7 years ago
Please see my comments on the original issue
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!
This issue was originally opened by @Stono as hashicorp/terraform#15601. It was migrated here as a result of the provider split. The original body of the issue is below.
Hi, This is a bit of both root terraform, and provider (google) so posting it here.
Terraform Version
Terraform Configuration Files
Too many, and too complex to paste. But in this example - we're doing a simple kubernetes version upgrade using the google_container_cluster resource.
Debug Output
Expected Behavior
Kubernetes to have been upgraded to 1.7.0 State file to have been updated to reflect 1.7.0 The "State Path" not to be null
Actual Behavior
Despite seeing "Apply complete! Resources: 0 added, 1 changed, 0 destroyed." Kubernetes remains on 1.6.6 State file in the gcloud bucket shows 1.6.6 State path is empty If I go and view the state file in GCS it was written (so its nothing permissions based) but shows 1.6.6