potiuk commented on PR #60074: URL: https://github.com/apache/airflow/pull/60074#issuecomment-3710123173
> The decision to not load provider configurations in shared library was kind of deliberate to keep the shared library agnostic of providers, but I guess we can have the sdk conf load the providers conf with an aim to stop providers relying on airflow-core and consuming from airflow task sdk instead? We can again do the same thing as with other shared libraries and `inject` configuration definition in the shared conf. How I imagine that to happen - shared conf should heve an "init" mathod where you could pass additional configuration entries - including provider configuration read by provider's manager. Then it is really a matter of proper sequence of initialization in each of the components * conf: inject_configuration_definition(airflow-core definition) * ProvidersManager() read_configuration * conf: inject_configuration (provider_configuration). This sequence should be done at the very beginning of every component start (and tests). This way conf will not have to know anything about providers. ProvidersManager will need to know configuration structure (and can use core configuration for whatever is needed) -> but then it would simply inject the new configuration list retrieved from providers into configuraiton, so that anything else can just read "configuration" without knowing if it came from providers os core. -- 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]
