aeroyorch opened a new issue, #58256: URL: https://github.com/apache/airflow/issues/58256
### Description We would like to extend the Flask AppBuilder (FAB) provider in Airflow to support configuring the ```rate_storage_uri``` and ```rate_storage_options``` parameters without the need to modify the ```webserver_config.py``` file directly. This enhancement would allow these configurations to be set via environment variables or Airflow configuration options. Currently, users must [manually edit the ```webserver_config.py```](https://airflow.apache.org/docs/apache-airflow-providers-fab/stable/auth-manager/security.html#rate-limiting) file to adjust the rate limiter’s backend storage settings, which is cumbersome and less suitable for automated or containerized deployments, like Helm deployments. ### Use case/motivation This feature aims to improve production deployments of Airflow by enabling seamless integration with external rate-limiting backends (e.g., Redis). By allowing ```rate_storage_uri``` and ```rate_storage_options``` to be set dynamically, Airflow users could easily switch from in-memory rate limiting to more scalable backends such as Redis. A first proposal would be: * Adding both ```auth_rate_limit_storage_uri``` (string) and ```auth_rate_limit_storage_options``` (string - JSON) configuration parameters to the ```[fab]``` section. Default: ```memory://```. * (¿) Only support [```redis``` and ```redis+cluster``` storage backends](https://flask-limiter.readthedocs.io/en/stable/#configuring-a-storage-backend). ### Related issues _No response_ ### Are you willing to submit a 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]
