Add redis authentication support from Rmux to backend server #27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Redis authentication support from Rmux to the backend Redis server(s). The connection from a client to Rmux still will not support authentication. Rmux just gains the capability to use authentication when connecting to servers.
This was a requirement in our environment as our backend Redis server instances require authentication for security. We use Rmux as a local connection pooler on our worker servers.
This PR is based on the updated Go structure from our PR #26. In case you are not interested in the new Go structure we could rebase this PR on your
master.