Closed jlledom closed 1 month ago
Hmm, is there a JIRA for this?
Instead of monkey patching upstream protocol class, it is a much better approach to use our own class and use the upstream protocol class with the composition pattern. Like I commented here: https://github.com/3scale/apisonator/pull/350#issuecomment-2020501532
For me this worked very easy OOB. ALthough it's not necessary to be just a copy of it. Just to use the upstream protocol class instead of monkey patching it. Unless I miss some details...
Hmm, is there a JIRA for this?
No, Sorry. This comes from https://github.com/3scale/apisonator/pull/350. I forgot to mention it in the PR description. Anyway, this is not directly related to TLS so maybe it should have it's own Jira.
Edit: I created this one: https://issues.redhat.com/browse/THREESCALE-11061
@akostadinov @mayorova I renamed the branch to add THREESCALE-11061
to the name and Github automatically closed this issue. I opened https://github.com/3scale/apisonator/pull/390
This comes from of https://github.com/3scale/apisonator/pull/350.
Now the Async mode supports Redis logical databases, and honors URLs like
redis://localhost:6379/6
The support has been also added for sentinels. A typical config would look like this:
Jira: https://issues.redhat.com/browse/THREESCALE-11061