Terraform tries (and fails) to recreate database on database_instance while it is stopped.

[MattGson]

Community Note

• 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.

Terraform Version

0.14.5

Affected Resource(s)

• google_sql_database_instance
• google_sql_database

Terraform Configuration Files

resource "google_sql_database_instance" "some_db_instance" {
  database_version = "MYSQL_5_7"
  name             = "name"
  region           = var.region

  settings {
    activation_policy = "NEVER"
...

resource "google_sql_database" "some_db" {
  charset   = "utf8"
  collation = "utf8_general_ci"
  instance  = google_sql_database_instance.some_db_instance.name
  name      = "name"

  lifecycle {
    prevent_destroy = true
  }
}

Expected Behavior

Terraform should identify that the instance is stopped and not try to create sub-resources.

Actual Behavior

Error creating Database: googleapi: Error 400: Invalid request: Invalid request since instance is not running.

The database actually already exists. Terraform assumes it doesn't and tries to create it on the stopped instance.

Steps to Reproduce

1. Create instance with activation_policy = "NEVER"
2. Create database for the instance.
3. terraform apply

[edwardmedia]

@MattGson I can repro the error. But if you change the data to uppercase for charset (below), you should not see this error.

Here are things around here

1. because terraform saves charset to uppercase, it detects the difference and plans to update the database when you do subsequent apply. (This is a provider bug) Once you provide the uppercase data, the database recreation will not be in the plan and then you will not see above error.
2. If you purposely want to update the database along with the instance update, you will see above error. Because these (instance and db) are different resources, there is no way at the provider level to avoid this error. This is the same behavior as Enabling private nodes in GKE does not recreate the node pools #8243.

Does this make sense? I could put a fix for above uppercase issue later on but it think it might not be the one you originally reported. Do you agree?

resource "google_sql_database" "some_db" {
  charset   = "utf8" ---> "UTF8"

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!