ARSN-551: don't require x-amz-content-sha256 header to be signed#2590
Conversation
Hello leif-scality,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
1 similar comment
Hello leif-scality,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Temporary base failureI've had trouble contacting the git host. Just post a comment on this pull request to wake me up. |
1 similar comment
cdebd75 to
024d5e4
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## development/8.2 #2590 +/- ##
================================================
Coverage 71.41% 71.41%
================================================
Files 222 222
Lines 17916 17918 +2
Branches 3703 3728 +25
================================================
+ Hits 12795 12797 +2
Misses 5117 5117
Partials 4 4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
1b97f42 to
8e40c35
Compare
8e40c35 to
af610f2
Compare
|
ping |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
|
/create_integration_branches |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: git fetch
git checkout -B w/8.3/bugfix/ARSN-551-dont-require-x-amz-content-sha256-signed origin/development/8.3
git merge origin/bugfix/ARSN-551-dont-require-x-amz-content-sha256-signed
# <intense conflict resolution>
git commit
git push -u origin w/8.3/bugfix/ARSN-551-dont-require-x-amz-content-sha256-signedThe following options are set: create_integration_branches |
|
ping |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
|
/approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue ARSN-551. Goodbye leif-scality. The following options are set: approve, create_integration_branches |
In practice AWS does not require
x-amz-content-sha256to be signed. So we remove the requirement