Open chaitanya14 opened 1 year ago
Nice to see yah implemented what we were discussing earlier in the day. That should do the trick in terms of what the redis client needs, but only thing not sure of is the nil case if the client will do anything whacky on connection but looks like it checks for it being a string and nil would keep it out of trying to use any kinda auth.
Pongo tests results:
@chaitanya14 Can you split this into multiple PRs each with its own set of tests? That would be easier to track and manage. You can add 3 PRs one for each of the following features- Auth enabled redis-cluster. Consumer based routing. Rate-limiting client headers.
@chaitanya14 For easier review can you please split the PR into multiple PRs as explained above?
Summary
Added functionality to support authentication enabled redis-cluster, consumer based routing and rate-limiting client headers.
Full changelog
Issues resolved
15