fix: Use NextMarker if only prefixes are returned#1278
Merged
fviard merged 1 commit intos3tools:masterfrom Oct 4, 2022
Fumesover:master
Merged
fix: Use NextMarker if only prefixes are returned#1278fviard merged 1 commit intos3tools:masterfrom Fumesover:master
fviard merged 1 commit intos3tools:masterfrom
Fumesover:master
Conversation
Contributor
|
Merged, thank you very much! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, if s3cmd is used to list objects in bucket, and if only CommonPrefixes are returned, the cli will ignore the NextMarker field and will use the last given prefix.
This fix will consider using the NextMarker if it's present, and will fallback on the last given prefix in both cases. Copying the workflow of awscli