Do not filter SSL_CERT_REQS to solve an issue with Cron Schedulers #749
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.
Hi there!
This change fixes the following issue I had related to the new CronSchedulers.
Because I'm on Heroku I have to set
SSL_CERT_REQStoNoneHowever when I acces
/admin/django-rq/I noticed that my list of Cron Schedulers is empty. Some digging led me to the functionutils.get_cron_schedulers. This function fails because of[SSL: CERTIFICATE_VERIFY_FAILED]. Looking into the connection I noticed thatssl_cert_reqs=requiredwas in there. This was strange I thought. Digging some more led me to the functionconnection_utils.filter_connection_paramsthat filtered out mySSL_CERT_REQSsetting. When I addSSL_CERT_REQSto the whitelist it all works as expected and I can see my running scheduler on the Cron Schedulers overview onadmin/django-rq/.