-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloudsql instance suddenly gets recreated #2309
Comments
What was the plan like? |
Unfortunately, there was no seperate plan recorded, just only the apply. |
I tried a handful up different upgrades and was also not able to reproduce. Without seeing the plan or the full debug output with TF=DEBUG it's hard for us to understand what happened. |
I completely understand. Implementing the plan in our workflow to actually better see what's going on - so -if- it happens another time, we got more visibility. Not being able to reproduce makes this a hard problem. |
Closing for now. Feel free to reopen if you see it again. |
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! |
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
The apply should have left the instance in place.
Actual Behavior
The apply destroyed and recreated the db again.
Steps to Reproduce
The previous run of the instance was with provider version 1.19.0. We upgraded to 1.19.1, and then did a terraform apply. Unfortunately, I cannot reproduce the behavior, in isolated sandbox-projects.
I did compare statefiles before and after, and there is no relevant difference.
References
I looked at #2229 which was as far as I could see the only PR merged between 1.19.0 and 1.19.1 I could figure out that actually touched the CloudSQL resource. I'd rather have a system not recreate the database, but bail out with an error if there is an issue with the output gotten from the google API.
The text was updated successfully, but these errors were encountered: