S3 high level checksums #8933
Open
S3 high level checksums #8933
+288
−1
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
aemous
force-pushed
the
s3-high-level-checksums
branch
from
a479b9c
to
0201a02
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.
Issue #, if available:
Low-level
aws s3apicommands support checksums other than MD5 for verifying end-to-end data integrity. This pull request ports over similar functionality to high-levelaws s3commands.Description of changes:
--checksum-algorithmflag for file uploads usingaws s3 cp,aws s3 sync, andaws s3 mv.--checksum-modeflag for file downloads usingaws s3 cp,aws s3 sync, andaws s3 mv.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.