Closed aleks-m closed 4 years ago
You can set disable_on_destroy
to false
during the transition, as shown in the example. You may need to commit the value first by running terraform apply
while the old bigquery service name is still set (Terraform doesn't read the new value from config during destroys).
Sorry! That part of the upgrade ended up a little less smooth than we expected.
For what it's worth, you probably don't need to manage that service at all anymore. It's enabled by default on all projects, and it's depended on by a couple of high-priority services, particularly container.googleapis.com
.
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!
Hi.
I am trying to upgrade Google provider in my configs from 2.20.0 to 3.9.0. I know what
bigquery-json.googleapis.com
has been renamed tobigquery.googleapis.com
in 3.x. I made a corresponding change in configs and got this onterraform apply
:Config snippet:
From https://www.terraform.io/docs/providers/google/guides/version_3_upgrade.html#resource-google_container_cluster:
Why is it trying to recreate a service in such destructive way instead? I can't add
disable_dependent_services=true
and disable all those services on a production environment. Is there any other way to solve this issue? What can you recommend?Thanks.