Fix VaultClient errors not being properly forwarded#5827
Fix VaultClient errors not being properly forwarded#5827bert-e merged 2 commits intodevelopment/9.0from
Conversation
This bump introduces a fix to VaulClient errors not being properly returned as Arsenal errors Issue: CLDSRV-666
Hello kerkesni,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
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 |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## development/9.0 #5827 +/- ##
================================================
Coverage 75.84% 75.84%
================================================
Files 188 188
Lines 11963 11963
================================================
Hits 9073 9073
Misses 2890 2890
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
/approve |
|
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-666. Goodbye kerkesni. The following options are set: approve, create_integration_branches |
Issue: CLDSRV-666