Skip to content
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

INTEGRATION [PR#5626 > development/8.7] Fixup on deleteObject #5633

Merged

Conversation

bert-e
Copy link
Contributor

@bert-e bert-e commented Jul 15, 2024

This pull request has been created automatically.
It is linked to its parent pull request #5626.

Do not edit this pull request directly.
If you need to amend/cancel the changeset on branch
w/8.7/bugfix/CLDSRV-555-deleteObjects-policy-eval-fix, please follow this
procedure:

 $ git fetch
 $ git checkout w/8.7/bugfix/CLDSRV-555-deleteObjects-policy-eval-fix
 $ # <amend or cancel the changeset by _adding_ new commits>
 $ git push origin w/8.7/bugfix/CLDSRV-555-deleteObjects-policy-eval-fix

Please always comment pull request #5626 instead of this one.

benzekrimaha and others added 4 commits July 15, 2024 14:20
Introduced by #5580
we now do send a requestContext with no specific resource instead
of "null", which results in a policy evaluation error.
As we get an implicit deny for the requestType "objectDelete",
cause the processed result to be false , thus sending an empty
array of objects to vault , resulting in a deny even when the policy
allows the action on specific objects.

Linked Issue : https://scality.atlassian.net/browse/CLDSRV-555
…mp/octopus/w/7.70/bugfix/CLDSRV-555-deleteObjects-policy-eval-fix
… into tmp/octopus/w/8.6/bugfix/CLDSRV-555-deleteObjects-policy-eval-fix
…into tmp/octopus/w/8.7/bugfix/CLDSRV-555-deleteObjects-policy-eval-fix
@bert-e bert-e mentioned this pull request Jul 15, 2024
@bert-e bert-e merged commit 22887f4 into development/8.7 Jul 15, 2024
15 checks passed
@bert-e bert-e deleted the w/8.7/bugfix/CLDSRV-555-deleteObjects-policy-eval-fix branch July 15, 2024 12:35
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.

2 participants