-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
redis cache - add support for TLS/encryption in transit #410
redis cache - add support for TLS/encryption in transit #410
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need a changelog fragment (minor_changes:
).
The test
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides that, LGTM.
Co-authored-by: Felix Fontein <felix@fontein.de>
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shipit
SUMMARY
tls://
prefix added onto the connection uri.Current connection string looks like this:
localhost:6379:0:changeme
.With this change, above still works, but if you need TLS now you can do:
tls://localhost:6379:0:changeme
.ISSUE TYPE
COMPONENT NAME
redis.py
ADDITIONAL INFORMATION
The connection uri in this plugin is split on
:
and then each element is sent verbatim positionally to theRedis
library's constructor, which works great for thehost
,port
,db
,password
params as they are the first four.But the
ssl
param is way down the list at number 17, so having to supply all those other values that are almost surely defaulted, doesn't really make sense.I added support to use a prefix, but otherwise didn't change anything about the uri, so it still just works just the same as it did and existing connection strings won't be affected.