-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update S3LayerDeleter to consider AWS SDK request limit #3372
Update S3LayerDeleter to consider AWS SDK request limit #3372
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for your (first) contribution! 🎉 🎉 🎉 🎉 I left just a couple of comments to move limit into the API and cleanup the code.
One more thing! Could you sign ECA please to make Eclipse license checker happy?
(Eclipse grabs your name and email from the commit, so doublecheck that you commited under the correct email (that was used to sign ECA), right now the ECA is required for thezachary[at]****.io
email).
…e iteration of objects to delete
Wondering if we should be returning the status or even the unsuccessfully deleted objects of the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! 🎉 ECA looks good as well.
Could you move that consturctor overload into the companion object?
@zacharyDez that's a good move, however, it requires a separate issue I guess. We have LayerDeleters for our other backends so the error encoding should be synchronized with all of them. I agree that it could be a very nice improvement 👍 @zacharyDez would you mind creating an issue to track down this idea? |
Opened the new issue #3373 @pomadchin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Merging once CI is green 🎉
And thanks for filing the follow up issue!
Thanks for your feedback with the PR! 🙏 |
Overview
Very straightforward fix to deal with the delete request limit of the AWS SDK.
Simply chunks the
objectIdentifiers
list into lists of length smaller than therequestLimit
and iteratively makes the delete call to the AWS SDK.Checklist
docs
guides update, if necessaryDemo
TODO
Notes
Unsure of the testing strategies favored for S3 and if the changes should be included in the changelog.
Closes #3371