potiuk commented on PR #41798: URL: https://github.com/apache/airflow/pull/41798#issuecomment-2315775269
> That would be awesome indeed! But, as mentioned by Ash at the last dev call, we need to find a solution for the auth manager. They are currently in providers and they are used by the webserver It's a bit spinning-off the Pydantic discussion but yes - having a "webserver-only plugin" or smth would be the best. We could define those independently from providers - same with remote logging. I do not think this should be a separate workstream targeted for 3.0 (it could possibly be done later) - but there is nothing wrong in installing "just" amazon provider in webserver when you need the loggging/auth - or we could potentially carve-out "Auth/Logging" out of provider to separate package. Currently the way airflow webserver works - you need to install all providers your DAGs can use, and if you have conflicts with any of them - you have a problem. But if you only install "amazon auth" and "amazon logging" - (for example) - which might be from amazon provider or it might be from a "webserver plugin" - and we do not need to install any other provider - that changes a lot when it comes to conflicting dependencies. If we we could just move connections and base operator links out - that would remove the need to install all the providers you want to use in your DAGs for webserver - and only install single auth/loging that is "per-installation". -- 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]
