Repository navigation
CLDSRV-1060: Check the governance bypass permission on DeleteObject (hotfix/9.2.36) - #6360
Conversation
Hello leif-scality,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I expected to find at least:
Please check the |
|
LGTM |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
... and 2 files with indirect coverage changes @@ Coverage Diff @@
## hotfix/9.2.36 #6360 +/- ##
=================================================
- Coverage 84.36% 84.32% -0.04%
=================================================
Files 204 204
Lines 13162 13162
=================================================
- Hits 11104 11099 -5
- Misses 2058 2063 +5
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
LGTM |
dvasilas
left a comment
There was a problem hiding this comment.
Prefex using cherry-pick -x so that we get cherry picked from ... and we can find the initial commit.
The bypass action was added to the authorization only when sourceVersionId was set, which is the version of a copy source and is never set on a delete. So a delete of a specific version with x-amz-bypass-governance-retention removed a GOVERNANCE-locked version with only s3:DeleteObjectVersion, and a Deny on s3:BypassGovernanceRetention was ignored. Authorize s3:BypassGovernanceRetention on every delete of a specific version that sends the header. Call prepareRequestContexts in the unit tests as the API does for a delete, without a copy source, and add functional tests with IAM users against Vault. (cherry picked from commit 8cfe61b)
9.2.36 has neither the AWS SDK v3 nor the IAM test helper, so create the IAM users with the v2 IAM client, as bucketPolicyBypassPort.js does.
The latest is 26 with breaks with tests needing python 3.9 (cherry picked from commit 8d58737)
a6a2d10 to
3e47956
Compare
|
LGTM |
|
/approve |
Incorrect fix versionThe
Considering where you are trying to merge, I expected to find at least:
Please check the The following options are set: approve |
|
ping |
|
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-1060. Goodbye leif-scality. The following options are set: approve |
Cherry-picked from #6354. The conflicts were formatting only. 9.2.36 has no AWS SDK v3, so the functional test uses the v2 SDK and creates its IAM users itself.