Replies: 2 comments 1 reply
-
Hey @idahogray 👋, We also offer priority support for our sponsors. |
Beta Was this translation helpful? Give feedback.
-
@auvipy Hello, I'd like to work on this feature for celery as I'd love to incorporate it in my project. We'd probably need to update: Would I have the green light for doing this? |
Beta Was this translation helpful? Give feedback.
-
Checklist
for similar or identical enhancement to an existing feature.
for existing proposed enhancements.
to find out if the if the same enhancement was already implemented in the
master branch.
(If there are none, check this box anyway).
Related Issues and Possible Duplicates
Related Issues
Possible Duplicates
Brief Summary
Rabbitmq supports verifying client's using a TLS keyfile. Celery supports this with one exception, the keyfile cannot be password
protected. I believe the underlying Python SSL library does support this so I am wondering if there is interest in adding that support
in Celery?
Design
Architectural Considerations
I believe Kombu would need updates as well as Celery.
Proposed Behavior
I propose adding a new element to the
broker_use_ssl
dict to provide the keyfile's password.{"keyfile_password": "some strong password"}
.Proposed UI/UX
I believe only the
broker_use_ssl
setting would need updated from a UI standpoint.Diagrams
N/A
Alternatives
The current feature works well, it just doesn't allow the keyfile to have a password. Therefore, a viable alternative is to
leave it the way it is.
Beta Was this translation helpful? Give feedback.
All reactions