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
# google_sql_database.database will be updated in-place
~ resource "google_sql_database" "database" {
~ deletion_policy = "ABANDON" -> "DELETE"
id = "projects/graphite-test-rileykarson/instances/myinstance/databases/mydb"
name = "mydb"
# (5 unchanged attributes hidden)
}
The deletion_policy change has 2 implicit steps as follows:
ALTER DATABASE [library-main] SET single WITH NO_WAIT.
ALTER DATABASE [library-main] SET multi_user WITH NO_WAIT.
In our production, there is an exception after the first step and the database access mode wasn't changed back, so all of the services can't connect to the DB anymore.
Could we expose the deletion_policy as a variable in this module? so we can give it a stable value
Terraform Resources
No response
Detailed design
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
TL;DR
hashicorp/terraform-provider-google-beta#4972
The deletion_policy change has 2 implicit steps as follows:
In our production, there is an exception after the first step and the database access mode wasn't changed back, so all of the services can't connect to the DB anymore.
Could we expose the deletion_policy as a variable in this module? so we can give it a stable value
Terraform Resources
No response
Detailed design
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: