-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Sentinel and connection string support #6
base: main
Are you sure you want to change the base?
Conversation
-Keys off of serviceName in the connectionString -Rebuilds config after running 'get-master-addr-by-name' on all available Sentinels -Updated naming conventions, removed errant whitespace
-Updated naming conventions for fields -Removed redundant qualifiers -Removed unused using
-Added new function to retrieve value from connectionString
Hi @cjb5790, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution! TTYL, AZPRBOT; |
Please add some unit tests and functional tests to test this behaviour. |
It would be awesome if Sentinel support would be added. Is there anything you need help with? |
@gonace Please add some unit tests and functional tests to test this behavior. |
whats the status of this pull request? |
What is the status of this pull request? |
I believe that this works now due to enhancements in StackExchange.Redis, as mentioned here. Is connecting to sentinels an issue you are still having? |
Utilizing the serviceName property within a connection string, the provider will now discover the master Redis instance and use that IP for it's connection. Support has also been added to use the existing connectionString node of the web.config.