Hey everyone, TL;DR; There is a small update to how our configuration works. Nothing major - generally everything **should be** backwards compatible. But please raise any issues you might have in #development channel (and tag me) if you see something that might be broken for you.
The few things I wanted to point out. * Airflow config is generated automatically as before if you do not have it This has not changed and should work as before. The one change that you will notice is that the generated file also contains (in comments) the environment variable name that corresponds to the configuration option - so that you can copy&paste it from there (small quality of life improvement that I saw as a really nice time-saver in a number of cases). Those generated files contain default values as "usual" * No more default config "file" in our repo When you look here: https://github.com/apache/airflow/blob/main/airflow/config_templates/default_airflow.cfg you will not find something that "looked like" default airflow configuration. It was not one, it was a JINJA template to generate it so if you just downloaded and used it, it would not work for log configuration and a few other things. Instead - this file now has instructions on what to do instead. * New way to generate default configuration Instead you can now generate the default configuration with `airffow config list --defaults` and redirect it to where you want. The nice thing is that this one has all the values commented out, so in order to change something you need to comment it out and change - it should be way easier to see what you have changed when you use it for "production" case. This is something we recommended to our users but we did not give them tools to do so. The `airflow config list` has many more options now - it became a "swiss-army-knife" for configuration generation. * Providers have their own configuration The big difference will be that if you have no celery provider installed, it will not contain celery configuration as it comes together with celery provider. We will have the configuration moved for other providers: cncf.kubernetes, atlas, etc. in the coming days. * More consistent approach for unit test configuration There used to be the AIRFLOW_HOME/unittest.cfg file generated automatically when you run unit tests, and in breeze it has been copied from another file. No more. All the defaults for unit tests are automatically overridden from https://github.com/apache/airflow/blob/main/airflow/config_templates/unit_tests.cfg and you do not have to think about it - the unit tests for configuration should work the same for local env and breeze. J. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
