[Cache][Messenger] Redis Sentinel configuration names are not streamlined even though they're doing exactly the same thing #52671
Labels
Comments
|
Let's support both keys everywhere. Up for a PR? |
fabpot
added a commit
that referenced
this issue
Dec 8, 2023
…nd sentinel_master available everywhere (xabbuh) This PR was merged into the 7.1 branch. Discussion ---------- [Cache][Messenger] make both options redis_sentinel and sentinel_master available everywhere | Q | A | ------------- | --- | Branch? | 7.1 | Bug fix? | no | New feature? | yes | Deprecations? | no | Issues | Fix #52671 | License | MIT Commits ------- 7c1bfcf make both options redis_sentinel and sentinel_master available everywhere
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symfony version(s) affected
6.3.5
Description
For Messenger, Redis Transport takes
sentinel_master.For Cache, Redis Adapter takes
redis_sentinelfor the same use.This creates friction where developers should reasonably expect the same configuration to have the same names. This is made worse by Cache DSN parser not reporting invalid config, which Messenger does.
How to reproduce
Check the docs.
Possible Solution
Streamline the namings.
Additional Context
No response
The text was updated successfully, but these errors were encountered: