[FEATURE] Add contentMD5 for putObject
to support object locking
#394
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.
Motivation
We are hitting an error when using this library because our bucket is configured with object locking:
The AWS S3 API requires passing the
Content-MD5
option forputObject
requests that target buckets with object locking enabled.From the
putObject
API description:This MR adds a BC support for passing an
Option[String]
as contentMD5, which is a base64 encoded MD5 hash. The library users will be responsible to provide a correct contentMD5.Urgency
This is extremely urgent for us since it blocks the go-live of an important project. So if you @regis-leray could have a look shortly and hopefully merge this change to the lib we could use a snapshot version to start our go-live. Thank you very much in advance!