Fix aws-nuke staling when there are a lot of S3Objects #101
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When there are a large number of s3object, aws-nuke fails Excluded because S3 bucket removal handles removing all S3Objects
fridim
force-pushed
the
GPTEINFRA-12752
branch
from
a83ed79 to
50bc457
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
GPTEINFRA-12752
aws-nukestale: when the account to cleanup has a lot of S3objects, with current config aws-nuke loops and fails.=> In the config, exclude S3Object entirely, because S3 bucket removal handles removing all S3Objects already.
ansible.cfgwithprofile_tasksto gather execution time of tasks