-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[NV-1804] Fix: Allow Distributed Cache to use Redis Password #2942
Conversation
I am still getting errors in my container built off of this branch about |
No longer getting the error after changing the tag on my docker image - seems to have been user error. The pipeline that failed seems to be a docker bug since I did not touch any docker stuff in this commit. Will fast-forward and see if that helps. |
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.
Thanks for adding the functionality for self hosted solutions. 🙌🏻
apps/api/src/app/shared/services/distributed-lock/distributed-lock.service.ts
Outdated
Show resolved
Hide resolved
apps/api/src/app/shared/services/distributed-lock/distributed-lock.service.ts
Show resolved
Hide resolved
Applied the suggestions - thank y'all! |
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.
🌟
What change does this PR introduce?
Supports Redis passwords in the distributed cache system.
Why was this change needed?
Fixes #2941.
Other information (Screenshots)
I just used the same connection object y'all were using for Bull. Figured it was probably closest to what y'all wanted.