potiuk commented on PR #60074: URL: https://github.com/apache/airflow/pull/60074#issuecomment-3708434389
I think for now (cc @amoghrajesh @kaxil @ashb) - the only good way is to make sure those defaults are also loaded by shared configuration. The issue is that those defauilts are coming from providers and you need to load provider's configuration before the defaults can be used, so this is an equivalent of pre-fetching defaults "just in case" before provider configuration is loaded. So option 3: > (Longer term) Extend SDK conf to also include provider fallback defaults > in its lookup chain I do not think "minimak changes" is a decision factor. Correctness is more important. The root cause is the same as described in https://github.com/apache/airflow/pull/60087#issuecomment-3708410863 -> we currently completely do not control the sequence in which different parts of airflow are initialized, this depends pretty much on the way how we import things -> in this case the problem is that we first retrieve the default values, before provider manager is initialized and defaults are retrieved. I think eventually, it will be fixed when we switch to explicit initialization of internal airflow shared functionalities -- 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]
