add missing header for put encrypted object#6122
Conversation
Hello sylvainsenechal,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
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 |
|
LGTM |
Codecov Report❌ Patch coverage is
Additional details and impacted files
... and 4 files with indirect coverage changes @@ Coverage Diff @@
## development/9.3 #6122 +/- ##
===================================================
- Coverage 84.31% 84.26% -0.06%
===================================================
Files 206 206
Lines 13251 13256 +5
===================================================
- Hits 11173 11170 -3
- Misses 2078 2086 +8
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Pull request overview
This PR addresses CLDSRV-879 by ensuring PUT Object responses include the expected server-side encryption (SSE) headers when an object is stored with encryption (either explicitly requested or applied via bucket default encryption).
Changes:
- Add SSE response headers to
objectPutresponses using the sharedsetSSEHeadershelper once the cipher bundle is created. - Extend functional tests to assert
PutObjectresponses includeServerSideEncryption(andSSEKMSKeyIdforaws:kms) in relevant scenarios.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| tests/functional/aws-node-sdk/test/object/encryptionHeaders.js | Adds assertions verifying PutObject responses include SSE-related response headers. |
| lib/api/objectPut.js | Sets SSE response headers for PUT responses based on the selected encryption config/cipher bundle. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
/create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
|
/approve |
Build failedThe build for commit did not succeed in branch w/9.4/bugfix/CLDSRV-879 The following options are set: approve, create_integration_branches |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-879. Goodbye sylvainsenechal. The following options are set: approve, create_integration_branches |
Issue: CLDSRV-879
Kinda need it because imma add functional tests in zenko, and these tests will depend on this