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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.
What should happen is nothing. It should be a noop.
Actual Behavior
I get an error:
Error: Error, failed to update instance settings for : googleapi: Error 400: Invalid request: Binary log must be disabled when backup is disabled or the instance must be a replica instance with a MySQL 5.7 or above version., invalid
Steps to Reproduce
turn on binary logging with backups turned off on a MySQL 5.7 replica
terraform apply
Important Factoids
I turned on binary logs on our replica via: gcloud sql instances patch --enable-bin-log. I spoke to google and this featured was enabled at the end of the year with:
slave_parallel_type
slave_parallel_workers
slave_preserve_commit_order
You have to turn on binary logs for commit_order. So this is a valid feature for the replica.
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Terraform v0.12.31
Affected Resource(s)
google_sql_database_instance
Terraform Configuration Files
Diff:
Expected Behavior
What should happen is nothing. It should be a noop.
Actual Behavior
I get an error:
Steps to Reproduce
turn on binary logging with backups turned off on a MySQL 5.7 replica
terraform apply
Important Factoids
I turned on binary logs on our replica via: gcloud sql instances patch --enable-bin-log. I spoke to google and this featured was enabled at the end of the year with:
You have to turn on binary logs for commit_order. So this is a valid feature for the replica.
Here is the google doc showing its supported: https://cloud.google.com/sql/docs/mysql/replication#bin-log-replica
The text was updated successfully, but these errors were encountered: