enhancement(aws_s3 source): Send content_md5 when writing objects #7936
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.
This is required when the bucket has object
locking
enabled, but also gives a bit more confidence that the object makes it
to S3 uncorrupted.
Unfortunately the test I added doesn't actually validate that Vector
works with object locked buckets due to a gap in
localstack but
I did verify it manually be creating a bucket with object locking
enabled, observing the failure, making the implementation change, and
observing the success.
Closes: #7310
Signed-off-by: Jesse Szwedko jesse@szwedko.me