-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass server-side encryption option to minio.StatObject call #142
Conversation
e8ae58b
to
1957544
Compare
Any updates on this one? |
Thanks for this PR! I'd love for this to be merged, my provider is using SSE-C and I cannot use Thanos because of the underlying issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Signed-off-by: Jens Hausherr <[email protected]>
Signed-off-by: Jens Hausherr <[email protected]>
Signed-off-by: Jens Hausherr <[email protected]>
Signed-off-by: Jens Hausherr <[email protected]>
Signed-off-by: Jens Hausherr <[email protected]>
Signed-off-by: Jens Hausherr <[email protected]>
Head branch was pushed to by a user without write access
@JoaoBraveCoding Rebasing onto main has reset the automerge for the PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Adds missing encryption data passed to
minio.StatObject()
calls, causing client methodsExists()
andAttributes()
to fail with a 400 Bad Request error.This may only affects encryption using
SSE-C
because here it is the callers responsibility to send the encryption key along with the request. In contrastSSE-KMS
andSSE-S3
are handled transparently (if the user has permissions to use the key in the casse ofSSE-KMS
)Fixes #141
Changes
Bucket.Exists()
Bucket.Attributes()
Verification
Added E2E-Test that uploads, checks for existence and downloads a file using SSE-C