potiuk commented on PR #53719: URL: https://github.com/apache/airflow/pull/53719#issuecomment-3114108623
> This is messier and more complex than I like -- any idea on w a way of cleaning this up greatly appreciated. We should change remote logging templates for loggers to be part of provider's packages as separate files that should be dropped to the same directory where "generic" airflow config is - and our logging configuration should discover the remote logging file dropped there and read it from there. Such remote logging config that should be copy*pasteable from provider's sources (and docs) should have everything needed for the core to be able to configure it in a generic way. That should remove the coupling of airlow core from essentially provider feature and make it a bit less messy. I am assuming your "messy" comment bit here is about precisely this - airflow-core needing to have some provider-specific parts. Maybe there are other "messy" parts that I do not realize :) -- 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
