potiuk commented on issue #37078: URL: https://github.com/apache/airflow/issues/37078#issuecomment-1916382058
No. This is wrong assessment. We already have few 100s of options in airflow config and we do not want to bloat it with even more stuff. Airflow config is actually one of the worst way to manage configuation, the best one in many deployments is setting configuration with environment variables, because it makes it far easier to manage changes in individual values and see them straight where you set them inthe Dockerfile. Nope . Our approach is that we only add new configuration when we absolutely need it, and if there is no other - easy - way to configure it. -- 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