RDS instance: Terraform insisting on destroy-recreate RDS instances although their IDs are unchanged #9760
Labels
service/rds
Issues and PRs that pertain to the rds service.
stale
Old or inactive issues managed by automation, if no further action taken these will get closed.
waiting-response
Maintainers are waiting on response from community or contributor.
This issue was originally opened by @dohoangkhiem as hashicorp/terraform#16724. It was migrated here as a result of the provider split. The original body of the issue is below.
We inspected our plan and realized Terraform keeps wanting to replace our RDS instances although their name, AZ have not changed, see below plan
The line
identifier: "group1-site1-live-5-5-6-public1" => "group1-site1-live-5-5-6-public1"
shows that no ID changes, and if we apply this it turns out that even availability zone does not change. But Terraform plan reports
id: "group1-site1-live-5-5-6-public1" => <computed> (forces new resource)
that makes me confused about the difference between
id
andidentifier
?How/why this plan could happen? We have another RDS instance which is almost the same as above but it's not in a list (so, count = 1) and the plan does not touch that instance (which is correct behaviour). Is this a bug?
There's a note that these existing RDS instances were imported to the state manually like following
Terraform version is 0.10.7, we tried with 0.10.8 and 0.11 and it's still the same plan.
The text was updated successfully, but these errors were encountered: