Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support configuring django-rq to use an SSL connection to Redis #3011

Closed
ajknv opened this issue Mar 15, 2019 · 1 comment
Closed

Support configuring django-rq to use an SSL connection to Redis #3011

ajknv opened this issue Mar 15, 2019 · 1 comment
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@ajknv
Copy link
Contributor

ajknv commented Mar 15, 2019

Environment

  • Python version: 3.6.8
  • NetBox version: 2.5.7

Proposed Functionality

Add support in Netbox configuration+settings for instructing django-rq to use SSL connections to Redis.

Use Case

Improves the security posture of the product using current feature support of Redis. Of special note, AWS ElastiCache does not permit the use of Redis AUTH without also enabling SSL transport.

Database Changes

None

External Dependencies

None. (Will need updated build of django-rq containing already-accepted pull request for enabling the SSL configuration parameter.)
@ajknv ajknv mentioned this issue Mar 15, 2019
Merged
@jeremystretch jeremystretch changed the title [Webhooks] Support configuring django-rq to use an SSL connection to Redis Support configuring django-rq to use an SSL connection to Redis Mar 15, 2019
@DanSheps DanSheps added the type: feature Introduction of new functionality to the application label Mar 15, 2019
jeremystretch added a commit that referenced this issue Mar 19, 2019
@jeremystretch
Changelog for #3011
7d1ee2e
@jeremystretch
Copy link
Member

Implemented by #3012

@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Mar 19, 2019
@jeremystretch jeremystretch mentioned this issue Apr 2, 2019
Merged
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DanSheps @jeremystretch @ajknv