vlazuka opened a new issue, #31027:
URL: https://github.com/apache/airflow/issues/31027

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### What happened
   
   Airflow 2.5.3
   
   Redis is attached using `rediss:...` url. While deploying the instance, it 
Airflow/Celery downgrades `rediss` to `redis` with the warning `[2023-05-02 
18:38:30,377: WARNING/MainProcess] Secure redis scheme specified (rediss) with 
no ssl options, defaulting to insecure SSL behaviour.`
   
   Adding `AIRFLOW__CELERY__SSL_ACTIVE=True` as an environmental variable (the 
same as `ssl_active = true` in `airflow.cfg` file `[celery]` section) fails 
with the error
   `airflow.exceptions.AirflowException: The broker you configured does not 
support SSL_ACTIVE to be True. Please use RabbitMQ or Redis if you would like 
to use SSL for broker.`
   
   ### What you think should happen instead
   
   It seems that Airflow doesn't recognize `rediss:...` url to be related to 
Redis broker
   
   ### How to reproduce
   
   Airflow 2.5.3
   
   Python 3.10.9
   Redis 4.0.14 (url starts with `rediss:...`)
   
   You need to add `AIRFLOW__CELERY__SSL_ACTIVE=True` as an environmental 
variable or `ssl_active = true` to `airflow.cfg` file `[celery]` section and 
deploy the instance
   
   
   ### Operating System
   
   Ubuntu 22.04.2 LTS
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   Heroku platform, heroku-22 stack, python 3.10.9
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to