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
When I run terraform apply on specific target which is affected it seems that everything is ok but finally default value "true" is still present in gcloud.
terraform apply output:
terraform apply -target module.aaa-bbb-c.google_compute_instance.bbb
google_compute_disk.bbb-boot: Refreshing state... (ID: aaa-bbb-c-0-boot)
google_compute_disk.bbb-data: Refreshing state... (ID: aaa-bbb-c-0-data)
google_compute_network.cloud-internal-netwrok: Refreshing state... (ID: cloud-internal-netwrok)
google_compute_subnetwork.cloud-internal-europe-west1: Refreshing state... (ID: europe-west1/cloud-internal-europe-west1)
google_compute_address.bbb-internal: Refreshing state... (ID: projects/abcd/regions/europe-west1/addresses/aaa-bbb-c-internal-0)
google_compute_instance.imf: Refreshing state... (ID: aaa-bbb-c-0)
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
~ module.syg-imf-c.google_compute_instance.imf
scheduling.0.automatic_restart: "true" => "false"
Plan: 0 to add, 1 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
module.aaa-bbb-c.google_compute_instance.bbb: Modifying... (ID: aaa-bbb-c-0)
scheduling.0.automatic_restart: "true" => "false"
module.aaa-bbb-c.google_compute_instance.bbb: Still modifying... (ID: aaa-bbb-c-0, 10s elapsed)
module.aaa-bbb-c.google_compute_instance.bbb: Modifications complete after 12s (ID: aaa-bbb-c-0)
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
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 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Nov 17, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On terraform 0.11.7 I try to change scheduling policy to not auto restart my VPS on GCE.
I'm using this in my affected module:
When I run terraform apply on specific target which is affected it seems that everything is ok but finally default value "true" is still present in gcloud.
terraform apply output:
gcloud describe command is still the same:
But when I change it manually in this case terraform see the change.
The text was updated successfully, but these errors were encountered: