-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
In-place upgrades for cloudsql resources #11903
Comments
@shuyama1 to assess feasibility |
@songalbert Sorry for the late investigation on this issue. It seems like we recently implemented the functionality of in-place major version upgrade for sql instance (GoogleCloudPlatform/magic-modules#6374). The feature is released in version 4.34.0. Is this something you are looking for? |
Closing this issue as it may have already implemented. Feel free to reopen this issue or create a new one if you think the feature is not yet supported in the providers. |
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. |
Community Note
Description
Terraform created cloudsql databases should be able to be upgraded in-place without causing issues of duplicate resources or hardcoded database versions. With the GCP console in-place upgrade feature available, it can cause problems if you are using terraform for your cloudsql maintenance.
New or Affected Resource(s)
google cloudsql postgres
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: