-
Notifications
You must be signed in to change notification settings - Fork 50
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
fix: override signing config for s3 control #1188
Conversation
A new generated diff is ready to view.
|
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.
It would be good to add an E2E test to make sure the operation continues to succeed
{ | ||
"id": "aef506d4-5c0b-4fa5-ac02-77ff09130875", | ||
"type": "bugfix", | ||
"description": "fix missing header (x-amz-content-sha256) in s3 control sigV4 operations", |
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.
nit: Proper capitalization and add --module s3control
flag when creating the changelog to make it service-specific, would appear something like this:
(s3control) Add missing x-amz-content-sha256
header for SigV4 requests
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
A new generated diff is ready to view.
|
Issue #
closes #1187
Description of changes
Apply the same signing config override that is used for s3 to s3 control
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.