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
We recently did some resizing our GCP instances to save cost. This would ideally go for reboot. We have observed that some of our engineers who are new to terraform not aware that the particular change that will be applied will go for reboot. This affected our live client.
Is their any way by which when we do terraform apply and if it requires to reboot the instance for sucessful completion then it should ask before doing reboot?
This change will require reboot. Do you want to proceed? Yes/no
Thanks,
Suvankar
The text was updated successfully, but these errors were encountered:
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
Jun 8, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
We recently did some resizing our GCP instances to save cost. This would ideally go for reboot. We have observed that some of our engineers who are new to terraform not aware that the particular change that will be applied will go for reboot. This affected our live client.
Is their any way by which when we do terraform apply and if it requires to reboot the instance for sucessful completion then it should ask before doing reboot?
This change will require reboot. Do you want to proceed? Yes/no
Thanks,
Suvankar
The text was updated successfully, but these errors were encountered: