Skip to content

Conversation

@0marperez
Copy link
Contributor

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.

@github-actions
Copy link

A new generated diff is ready to view.

  • No codegen difference in the AWS SDK

@0marperez 0marperez marked this pull request as ready for review January 22, 2024 19:14
@0marperez 0marperez requested a review from a team as a code owner January 22, 2024 19:14
Copy link
Member

@lauzadis lauzadis left a 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",
Copy link
Member

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

@sonarqubecloud
Copy link

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@github-actions
Copy link

A new generated diff is ready to view.

  • No codegen difference in the AWS SDK

@0marperez 0marperez merged commit 892336a into main Jan 23, 2024
@0marperez 0marperez deleted the s3-control-config-override branch January 23, 2024 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

S3 Control operation (createMultiRegionAccessPoint) fails with missing x-amz-content-sha256 header

3 participants