Closed tayyabgilani closed 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @tayyabgilani 👋 Thank you for taking the time to raise this! Assuming that nothing else is changing with the resources that you specified in your example configuration, I suspect this is related to the note on the availability_zones
argument in the aws_rds_cluster
resource's documentation. It mentions:
RDS automatically assigns 3 AZs if less than 3 AZs are configured, which will show as a difference requiring resource recreation next Terraform apply. We recommend specifying 3 AZs or using the
lifecycle
configuration blockignore_changes
argument if necessary.
Since you're only specifying 2 AZs, you're hitting the recreation requirement described here. This then changes the value of the cluster_identifier
for the aws_rds_cluster_instance
resources, which is also a force new operation.
To get around this, you can ignore changes to the aws_rds_cluster.availability_zones
argument, as described in that resources documentation, or supply a third AZ to get around that resource's recreation altogether.
Awesome, Thanks @justinretzolk 🥇
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.
Description
Terraform Version 1.4.6 AWS provider version 4.67.0
RDS cluster/instance resources
Plan Output
References
No response
Would you like to implement a fix?
None