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.
The replica instance remains unchanged and does not need to be recreated
Actual Behavior
encryption_key_name is required to be null for replica in same region. If you provide encryption_key_name anything other than null value for replica in same region you will receive following error.
Error: Error, failed to create instance instance-name-1: googleapi: Error 400: Invalid request: Disk encryption config should not be specified for replica that is in the same region of primary.., invalid
However, when you create with a null encryption_key_name, the google API returns the encryption_key_name for the main instance, now on the replica instance. this causes a drift on the state, and forces the replica to be recreated every terraform run
Steps to Reproduce
Create a sql database and replica with a CMEK. the replica must be in the same region as the main instance.
jmymy
changed the title
If using CMEK on Postgres with Replicas, the instance is recreated every terraform run
[google_sql_database_instance] If using CMEK on Postgres with Replicas, the instance is recreated every terraform run
Mar 14, 2022
jmymy
changed the title
[google_sql_database_instance] If using CMEK on Postgres with Replicas, the instance is recreated every terraform run
[google_sql_database_instance] If using CMEK on SQL instance with Replicas in the same region, the instance is recreated every terraform run
Mar 14, 2022
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
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
The replica instance remains unchanged and does not need to be recreated
Actual Behavior
encryption_key_name is required to be null for replica in same region. If you provide encryption_key_name anything other than null value for replica in same region you will receive following error.
Error: Error, failed to create instance instance-name-1: googleapi: Error 400: Invalid request: Disk encryption config should not be specified for replica that is in the same region of primary.., invalid
However, when you create with a null encryption_key_name, the google API returns the encryption_key_name for the main instance, now on the replica instance. this causes a drift on the state, and forces the replica to be recreated every terraform run
Steps to Reproduce
Create a sql database and replica with a CMEK. the replica must be in the same region as the main instance.
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: