RDS Cluster cannot be updated with replacement

[autarchprinceps]

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 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform 1.2.3
AWS Provider 4.21.0

Affected Resource(s)

• aws_rds_cluster
• aws_db_instance

Terraform Configuration Files

e.g. KMS change or snapshot change to force a replacement

~ kms_key_id = "arn:aws:kms:region:account:key/key_id1" -> "arn:aws:kms:region:account:key/key_id2" # forces replacement

Expected Behavior

The RDS cluster replacement needs to destroy resources depending on it, particularly the DB Instances, before deleting itself, and then recreating the dependant resources. Just like the cluster itself, they need replacement if their cluster changes, they cannot be assumed to be updatable in place.

Actual Behavior

Error: error deleting RDS Cluster (clustername): InvalidDBClusterStateFault: Cluster cannot be deleted, it still contains DB instances in non-deleting state.

[codezninja]

Just hit this issue as well. Any thoughts on how to fix this on the provider side? Currently my only workaround is to scale instances down to 0 before making destructive changes to the cluster