-
Notifications
You must be signed in to change notification settings - Fork 243
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
Improvement/cldsrv 430 delete api implicit deny #5470
Improvement/cldsrv 430 delete api implicit deny #5470
Conversation
ff186d8
to
b3ad1e6
Compare
Hello benzekrimaha,My role is to assist you with the merge of this Status report is not available. |
ping |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
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 |
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 |
2719387
to
6577286
Compare
/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/7.70/improvement/CLDSRV-430-delete-api-implicitDeny origin/development/7.70
$ git merge origin/improvement/CLDSRV-430-delete-api-implicitDeny
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/7.70/improvement/CLDSRV-430-delete-api-implicitDeny The following options are set: create_integration_branches |
ping |
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.6/improvement/CLDSRV-430-delete-api-implicitDeny origin/development/8.6
$ git merge origin/w/7.70/improvement/CLDSRV-430-delete-api-implicitDeny
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/8.6/improvement/CLDSRV-430-delete-api-implicitDeny The 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 |
/create_pull_requests |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
Follow integration pull requests if you would like to be notified of The following options are set: create_pull_requests, create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_pull_requests, create_integration_branches |
@bert-e reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: create_pull_requests, 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/7.70/improvement/CLDSRV-430-delete-api-implicitDeny origin/development/7.70
$ git merge origin/improvement/CLDSRV-430-delete-api-implicitDeny
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/7.70/improvement/CLDSRV-430-delete-api-implicitDeny The following options are set: create_pull_requests, create_integration_branches |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
4c2dd56
to
76b8d1f
Compare
History mismatchMerge commit #3303f5c8f77585901a9e300caff2f293db6be0a7 on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: create_pull_requests, create_integration_branches |
As for multiObjectDelete,a new function was added to ensure that all actions are allowed.
76b8d1f
to
74425d0
Compare
History mismatchMerge commit #2eeef31ff587fd0f6b08a3f2783d0c62019c7f56 on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: create_pull_requests, create_integration_branches |
@bert-e reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: create_pull_requests, 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/7.70/improvement/CLDSRV-430-delete-api-implicitDeny origin/development/7.70
$ git merge origin/improvement/CLDSRV-430-delete-api-implicitDeny
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/7.70/improvement/CLDSRV-430-delete-api-implicitDeny The following options are set: create_pull_requests, create_integration_branches |
ping |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
Follow integration pull requests if you would like to be notified of The following options are set: create_pull_requests, create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_pull_requests, create_integration_branches |
/approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve, create_pull_requests, 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-430. Goodbye benzekrimaha. |
Bucket policies are not correctly interpreted, this is part of the following epic to fix that: scality/Arsenal#2181
This PR is aiming to update get apis since object and bucket authorisations are made at API level and need to support implicit denies, ticket linked to this issue here : https://scality.atlassian.net/browse/CLDSRV-430
PRs providing implicit Deny logic to CS for processing in this PR
scality/Arsenal#2181
https://github.com/scality/Vault/pull/2135
#5322
#5420
#5432
#5456
#5462
Here CI links for zenko tests :
https://github.com/scality/Zenko/actions/runs/7130054302
https://github.com/scality/Zenko/actions/runs/7130071959
https://github.com/scality/Zenko/actions/runs/7130085996