CloudFormation: Allow deletion of deeply nested structures #7413
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.
Scenario: Resource A depends on resource B
When CloudFormation tries to delete both resources, it will do so in an unspecified order.
If CF tries to delete resource B first, it will fail because A depends on it
CloudFormation continues with the deletion of resource A (and any other unrelated resources)
Because B is not yet deleted, CF will iterate over the remaining resources. Nothing depends on resource B anymore, so it will be deleted successfully.
This was already implemented, but with the caveat that we would only iterate over the list of remaining resources up to 5 times.
With this change, we will iterate as long as we are deleting some resources per iteration, i.e.: there is some progression. This has two benefits:
Related: #7381