You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
ghost
locked and limited conversation to collaborators
Apr 7, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
0.8.5
Affected Resource(s)
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.
The text was updated successfully, but these errors were encountered: