Allow disabling Redis SSL verification for rediss schema

[amureki]

Certain services (like Heroku) do require disabling SSL certificate verification for their rediss schema:

They do require disabling the certificate validation - https://devcenter.heroku.com/articles/connecting-heroku-redis

This PR is aiming to adjust the client to be able to accept REDIS_CERT_REQS and pass it in such cases.

[codingjoe]

That URL scheme is natively supported https://github.com/redis/redis-py/blob/2e46613dcdf9db7f948f3258fee1c9199da8cbfa/redis/connection.py#L1163

[amureki]

@codingjoe you are right, but I did not finish working on this PR and did not elaborate properly (thus wrong description/title).

I am referring to the way Heroku (and a couple of other providers) work with rediss schema:

They do require disabling the certificate validation - https://devcenter.heroku.com/articles/connecting-heroku-redis

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.66%. Comparing base (72e8f1c) to head (98faeb0).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #129      +/-   ##
==========================================
+ Coverage   95.57%   95.66%   +0.09%     
==========================================
  Files          19       20       +1     
  Lines         610      623      +13     
==========================================
+ Hits          583      596      +13     
  Misses         27       27              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[codingjoe]

Please use redis' native parse_url function and override the single parameter. I would also suggest injecting the value of the parameter via an environment variable, since this is a Heroku problem.

[amureki]

Please use redis' native parse_url function and override the single parameter. I would also suggest injecting the value of the parameter via an environment variable, since this is a Heroku problem.

Yeah, my initial attempt of doing so failed, as it "magically" uses different connections based on the schema provided.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ TypeError: Redis.init() got an unexpected keyword argument 'connection_class' sam.redis_utils in async_redis_client View Issue

_{Did you find this useful? React with a 👍 or 👎}