storage: handle errors in batch objects delete action #627
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
kobajagi
force-pushed
the
predrag/sc-99100/exo-cli-storage-deleteobjects-error-handling
branch
from
1863f26 to
249ce04
Compare
sauterp
approved these changes
Oct 22, 2024
kobajagi
deleted the
predrag/sc-99100/exo-cli-storage-deleteobjects-error-handling
branch
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.
Description
Batch objects delete API method from
aws-sdk-go-v2will not return error as second argument if individual objects failed to be deleted. Instead it will return both list of deleted objects and list of errors in result structure.This prints errors (if any) after the list of successfully deleted files.
Checklist
(For exoscale contributors)
Testing