[GitHub] [airflow] potiuk commented on pull request #22588: Print configuration on scheduler startup.

[GitBox <gi...@apache.org>]

potiuk commented on pull request #22588:
URL: https://github.com/apache/airflow/pull/22588#issuecomment-1084530946


   > Couple things: I think we should only show non-default config (I'm not sure if this is already the case, but I don't think it is) and should we do this for other components also?
   
   I fully agree we should have it for all components. However I think showing complete config is a bit better. Ideally it should also show where the config came from =- default, config file, variable, secret. And this might need a bit modification of the conf code. But I tink it is crucial part of this change - knowing wheree each configuration variable came from would make it infintely easier to diagnose problems of people who - for example - have systemd and do not realize their `AIRFLOW___` variable is not set  when their server is started but they have it set when the login interactively and their .bashrc is actually sourced then.
   
   Not seeing the config values  currently is the major source of problems (I've seen multiple issues about it) for people who do not realize that `airflow info` can actually produce different set of configuration than whan their webserver or scheduler sees.
   
   Such misconfigurations are next to impossible to diagnose currently, they rely mostly on guessing.
   
   Note that gunicorn makes it a bit difficult for webserver because it will print logs every time gunicorn restarts the process which makes it rather annoying - so this information shoudl only be printed in the main process of webserver. 
   


-- 
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-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org