Closed KazToozs closed 1 year ago
My role is to assist you with the merge of this
pull request. Please type @bert-e help
to get information
on this process, or consult the user documentation.
Status report is not available.
This pull request's source branch improvement/ARSN-362-impDeny
has diverged from
development/8.1
by more than 50 commits.
To avoid any integration risks, please re-synchronize them using one of the following solutions:
origin/development/8.1
into improvement/ARSN-362-impDeny
improvement/ARSN-362-impDeny
onto origin/development/8.1
Note: If you choose to rebase, you may have to ask me to rebuild
integration branches using the reset
command.
The Fix Version/s
in issue ARSN-362 contains:
7.70.10
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
7.10.48
7.70.10
8.1.110
Please check the Fix Version/s
of ARSN-362, or the target
branch of this pull request.
Must make variables consistent between clients https://github.com/scality/Arsenal/pull/2162#pullrequestreview-1615732187
The Fix Version/s
in issue ARSN-362 contains:
7.10.48
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
7.10.48
7.70.10
8.1.110
Please check the Fix Version/s
of ARSN-362, or the target
branch of this pull request.
Must make variables consistent between clients https://github.com/scality/Arsenal/pull/2162#pullrequestreview-1615732187
done
ping
I have created the integration data for the additional destination branches.
improvement/ARSN-362-impDeny
into
development/7.10
development/7.70
development/8.1
The following branches will NOT be impacted:
development/6.4
development/7.4
You can set option create_pull_requests
if you need me to create
integration pull requests in addition to integration branches, with:
@bert-e create_pull_requests
The following approvals are needed before I can proceed with the merge:
the author
2 peers
Opened after closed PR here
Adds ImplicitDeny logic to policy checks, where an ImplicitDeny will be sent back in case no policy validates an action, but does not explicitly Deny it either, allowing for bucket policies and other authorization mechanisms to grant permission.
Part of the bucket policy redo epic: https://scality.atlassian.net/jira/software/c/projects/OS/boards/214?modal=detail&selectedIssue=S3C-7756
Green build in Vault and CS: https://github.com/scality/Vault/actions/runs/6151692989/job/16692302075?pr=2135 https://github.com/scality/cloudserver/actions/runs/6157396066/job/16708032893?pr=5322