feat: Add create_before_destroy
to Aurora DB instance resource
#506
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add a
create_before_destroy
lifecycle block to theaws_rds_cluster_instance
resources.Motivation and Context
This improves time to recover in the (uncommon) case where the DB instances have to be replaced, for example to change their identifier or network configuration. We have observed that it can take nearly 10 minutes to destroy an Aurora instance. And then a similar time to create its replacement. During this time the DB is inaccessible. By using
create_before_destroy
, there is only a small interruption while one of the new instances is promoted to the Writer role. Which seems to typically take less than 30 seconds.Breaking Changes
N/A
How Has This Been Tested?
pre-commit run -a
on my pull requestThere is nothing to change in the
examples
, everything is internal to the code of the module.