-
Notifications
You must be signed in to change notification settings - Fork 9.7k
Closed
Labels
breaking-changeIntroduces a breaking change in current functionality; usually deferred to the next major release.Introduces a breaking change in current functionality; usually deferred to the next major release.enhancementRequests to existing resources that expand the functionality or scope.Requests to existing resources that expand the functionality or scope.service/rdsIssues and PRs that pertain to the rds service.Issues and PRs that pertain to the rds service.
Milestone
Description
This issue was originally opened by @adrianlop as hashicorp/terraform#11636. It was migrated here as part of the provider split. The original body of the issue is below.
Terraform Version
0.8.5
Affected Resource(s)
- aws_db_instance
Expected Behavior
Using AWS RDS UI you can change the identifier and it won't recreate the database, it will only apply it on the preferred maintenance window/apply immediately if you select it.
This change also changes the endpoint, so AWS will give you a warn as expected: Warning! Endpoint will also change
.
Actual Behavior
Terraform will destroy + recreate the instance. It should only apply the change in the maintenance window or immediately if you selected apply_immediately=true
, not destroy the DB.
Thanks.
tomhaynes, maxd, nicoleyson, markmsmith, AngryUbuntuNerd and 55 more
Metadata
Metadata
Assignees
Labels
breaking-changeIntroduces a breaking change in current functionality; usually deferred to the next major release.Introduces a breaking change in current functionality; usually deferred to the next major release.enhancementRequests to existing resources that expand the functionality or scope.Requests to existing resources that expand the functionality or scope.service/rdsIssues and PRs that pertain to the rds service.Issues and PRs that pertain to the rds service.