[Feature] Add backward-compatible TLS unauthorized support to Redis bull connections #5784
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
|
|
n8n-assistant
bot
added
community
|
This is being tracked internally as |
Joffcom
added
the
in linear
|
Thanks for the PR. But, TLS support for redis was added here. If you need to use self-signed certificates, We recommend adding your root CA cert to your OS, or in case of docker adding the root CA cert to volume mounted at |
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.
Github issue / Community forum post (link here to close automatically):
Supplementary from this PR: #3113
Code all copied from this community post: https://community.n8n.io/t/redis-tls-support-for-bull-in-queue-mode/17522
The code is backward-compatible and opens support for modern Redis servers.