Send signatureVersion and authType unswapped to Vault checkPolicies - #6239
Conversation
multiObjectDelete assigned authType to signatureVersion and vice versa when building the checkPolicies request context, so Vault validated and evaluated each field against the wrong value. Issue: CLDSRV-963
Hello benzekrimaha,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 ignored possible hotfix versions and I expected to find:
Please check the |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check 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 |
|
/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/9.2/improvement/CLDSRV-963-fix-swapped-auth-params-check-policies origin/development/9.2
git merge origin/improvement/CLDSRV-963-fix-swapped-auth-params-check-policies
# <intense conflict resolution>
git commit
git push -u origin w/9.2/improvement/CLDSRV-963-fix-swapped-auth-params-check-policiesThe following options are set: create_integration_branches |
|
Integration branch |
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/9.3/improvement/CLDSRV-963-fix-swapped-auth-params-check-policies origin/development/9.3
git merge origin/w/9.2/improvement/CLDSRV-963-fix-swapped-auth-params-check-policies
# <intense conflict resolution>
git commit
git push -u origin w/9.3/improvement/CLDSRV-963-fix-swapped-auth-params-check-policiesThe following options are set: create_integration_branches |
|
Integration branch |
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/9.4/improvement/CLDSRV-963-fix-swapped-auth-params-check-policies origin/development/9.4
git merge origin/w/9.3/improvement/CLDSRV-963-fix-swapped-auth-params-check-policies
# <intense conflict resolution>
git commit
git push -u origin w/9.4/improvement/CLDSRV-963-fix-swapped-auth-params-check-policiesThe following options are set: create_integration_branches |
|
Integration branch |
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 |
History mismatchMerge commit #21a5ae9515c392527f62171b0fc879038716f81f 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 |
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 |
History mismatchMerge commit #39a5e96319a9a84100c04d190fd86af62dcd7d07 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 |
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 |
History mismatchMerge commit #3d83c119356101dccbbdea05430e9ba476fce84a 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 |
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 |
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 @@
## development/9.1 #6239 +/- ##
===================================================
+ Coverage 83.85% 83.97% +0.12%
===================================================
Files 191 191
Lines 12352 12352
===================================================
+ Hits 10358 10373 +15
+ Misses 1994 1979 -15
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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 |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
This pull request did not target the following hotfix branch(es) so they
Please check the status of the associated issue CLDSRV-963. Goodbye benzekrimaha. The following options are set: approve, create_pull_requests, create_integration_branches |
Summary
multiObjectDeleteswappedsignatureVersionandauthTypewhen building thecheckPoliciesrequest context sent to Vault, so each field was validated and evaluated against the other's value. Found while investigating RD-1890 (VeeamDeleteObjectsfailures).Issue: CLDSRV-963