shayoo9814 commented on issue #37078: URL: https://github.com/apache/airflow/issues/37078#issuecomment-1915906602
I still believe there is value to be gained from the proposed change for the following reasons. 1. Consistent interface for Airflow customizations `airflow.cfg` is what users recognize as the established interface through which they can override/customize various configurations (e.g., `logging_config_class` and `celery_config_options`). Why not keep things consistent and allow Airflow users to customize Celery logging through `airflow.cfg`? 2. GUNICORN_CMD_ARGS is harder to manage than `airflow.cfg` In our case, we have to add this ENV in our Dockerfile and custom startup scripts, which is more work compared to modifying `airflow.cfg` -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
