-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
In 2.16 several changes were made to the way the Redis connection URLs are handled, specifically, adding ways to provide username and password in the URLs, identifying whether the connection is to support SSL, etc.
Related Jiras:
https://issues.redhat.com/browse/THREESCALE-11205
https://issues.redhat.com/browse/THREESCALE-11076
https://issues.redhat.com/browse/THREESCALE-11070
https://issues.redhat.com/browse/THREESCALE-11062
https://issues.redhat.com/browse/THREESCALE-11021
https://issues.redhat.com/browse/THREESCALE-11850
The content for the doc needs to be fetched from all the above Jiras.
- documents
-
THREESCALE-11205 Accept sentinels credentials in the redis URI
-
- Closed
-
-
THREESCALE-11850 Preflight check fails on redis-sentinel
-
- Closed
-
-
THREESCALE-11076 Sidekiq: Extract the `:ssl` param from the Redis URL
-
- Closed
-
-
THREESCALE-11021 Add a way for the client to provide redis ACL credentials to system and backend
-
- Closed
-
-
THREESCALE-11062 Add support for Sidekiq + Sentinels + Redis Logical DBs
-
- To Test For On-Prem
-
-
THREESCALE-11070 Sidekiq: Extract Sentinels group name from the URL
-
- To Test For On-Prem
-