CLDSRV-717: Fix & drop config root redis for utapi#5891
CLDSRV-717: Fix & drop config root redis for utapi#5891bert-e merged 1 commit intodevelopment/9.0from
Conversation
Hello bourgoismickael,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 |
Codecov Report❌ Patch coverage is
Additional details and impacted files
@@ Coverage Diff @@
## development/9.0 #5891 +/- ##
================================================
Coverage 83.10% 83.11%
================================================
Files 188 188
Lines 12048 12046 -2
================================================
- Hits 10013 10012 -1
+ Misses 2035 2034 -1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Currently, root redis is not defined neither by zenko or s3c. This breaks utapi replay with overrided redis config. There has been multiple tickets S3C-1399 ZENKO-345 ZENKO-1051 ZENKO-3294 In the end root redis is not used and utapi should use utapi.redis and cloudserver uses localCache.
a4728f0 to
33e571e
Compare
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 |
|
/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-717. Goodbye bourgoismickael. The following options are set: approve, create_integration_branches |
Currently, root redis is not defined neither by zenko or s3c. This breaks utapi replay with overrided redis config.
There has been multiple tickets S3C-1399 ZENKO-345 ZENKO-1051 ZENKO-3294
In the end root redis is not used and utapi should use utapi.redis and cloudserver uses localCache.