fix(dbcluster) - Add delay to Aurora Serverless V2 update changes #609
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 of changes:
Add a delay to Aurora Serverless V2 updates, because whilst the DBCluster completes immediately, asynchronous workflows occur after the DBCluster resource is updated.
Whilst the DBCluster resource is being updated in these asynchronous workflows, resources such as DBInstances are locked out from being rebooted - but they require reboots if there are updates to DBInstances and DBParameterGroups are set to pending-reboot status.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.