[Bug]: aurora global cluster keep recreating if new global cluster from existing primary cluster which has database_name

[wangyi198682]

Terraform Core Version

Terraform v1.9.0

AWS Provider Version

5.45.0

Affected Resource(s)

No response

Expected Behavior

no drift or no diffs when terraform plan again.

Actual Behavior

after second round run terraform plan or apply, we saw that it tries to recreate global cluster.

- database_name                = "mydb" -> null # forces replacement

and it recreates global cluster, this will cause global cluster's members being removed.

aws_rds_global_cluster.this[0]: Destroying... [id=example]
aws_rds_global_cluster.this[0]: Destruction complete after 3s
aws_rds_global_cluster.this[0]: Creating...
aws_rds_global_cluster.this[0]: Creation complete after 0s [id=example]

Apply complete! Resources: 1 added, 0 changed, 1 destroyed.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_rds_cluster" "primary" {
  //other configurations
  database_name   = "mydb"
  lifecycle {
    ignore_changes = [global_cluster_identifier]
  }
}

resource "aws_rds_global_cluster" "example" {
  force_destroy                = true
  global_cluster_identifier    = "example"
  source_db_cluster_identifier = aws_rds_cluster.primary.arn
}

Steps to Reproduce

step1: terraform plan & apply. step2: after all the resources created, then run terraform plan again.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[wangyi198682]

and I solve it by using following change to "aws_rds_global_cluster"

lifecycle {
    ignore_changes = [   
      database_name,
    ]
  }

[justinretzolk]

Similar #28187