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.

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

Support Redis + TLS URLs #2833

Closed
dstufft opened this issue Oct 1, 2015 · 15 comments
Closed

Support Redis + TLS URLs #2833

dstufft opened this issue Oct 1, 2015 · 15 comments

Comments

@dstufft
Copy link

dstufft commented Oct 1, 2015

redis-py supports redis instances which are secured by TLS by using rediss://URLs instead of redis:// URLs. Celery should support this too.

@ask
Copy link
Contributor

ask commented Dec 12, 2015

Does it not have an option for that? Or is this a special option that can only be set in the new url format?

@dstufft
Copy link
Author

dstufft commented Dec 13, 2015

Celery doesn't know that rediss:// (note the two s) is a redis backend. See https://github.com/pypa/warehouse/blob/master/warehouse/celery.py

@ask
Copy link
Contributor

ask commented Dec 14, 2015

Yeah, but we don't pass this URL to Redis, we need an option to set

@dstufft
Copy link
Author

dstufft commented Dec 14, 2015

@ask
Copy link
Contributor

ask commented Jun 24, 2016

Closing this, as we don't have the resources to complete this task.

@ask ask closed this as completed Jun 24, 2016
@lern
Copy link

lern commented Feb 1, 2017

Any plan to support the rediss:// schema?

@smcoll
Copy link

smcoll commented Jul 25, 2017

How does this issue correspond to #3831?

@chriskuehl
Copy link
Contributor

It should work fine, we're using SSL on the broker and the backend for Redis. Broker support has been around for a while (not sure when it was added), backend support for SSL was added in #3831. I think this ticket can be closed.

Here are the docs:
http://docs.celeryproject.org/en/latest/userguide/configuration.html

The relevant options are redis_backend_use_ssl and broker_use_ssl (which has a section on redis).

@dstufft
Copy link
Author

dstufft commented Aug 31, 2017

Those options existed when I originally opened this issue, but this issue isn't about supporting TLS at all, it was specifically about supporting rediss:// URLs to turn on the TLS support.

@chriskuehl
Copy link
Contributor

The backend option definitely didn't exist when you opened the ticket (I added it in #3831 only a few months ago). But that's a good point, maybe the ticket should be re-opened.

@remeika
Copy link
Contributor

remeika commented May 1, 2018

I think this ticket should actually be broken out into two closely-related issues:

Celery processes the value of result_backend in its own code, and directly instantiates a redis connection from redis-py. But the value of broker_url is passed to Kombu, which also must be patched.

@gonzalodiaz
Copy link

+1 We need the fix from Kombu as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants