Closed flamarion closed 1 year ago
If we merge like this and update the module version in the deployer, it will trigger the upgrade immediately. I will put this on hold for now and discuss with @jsbroks the potential implementation of maintenance_version and available_maintenance_versions. With these setup I think we can let GCP do the work for us in the maintenance window.
We can merge this
It was closed as requested.
No need to close the pr, you have other changes worth merging
This PR is included in version 1.13.1 :tada:
The module defaults the MySQL version to the
8_0_29
, which is not supported by GCP anymore, and during the deployment, the following error comes up.The current default version for the
8_0
is the0_0_26
.https://cloud.google.com/sql/docs/mysql/db-versions
The idea is to test and validate the downtime time to upgrade the DB for the next minor version,
8_0_30
, considering that it will cause downtime according to the documentation.https://cloud.google.com/sql/docs/mysql/upgrade-minor-db-version#minor-ver-upgrade
the instance is restarted during the operation, which causes downtime.
From Terraform perspective, this is a change in place, but there's downtime as stated in the documentation.