potiuk commented on issue #51545: URL: https://github.com/apache/airflow/issues/51545#issuecomment-2980568210
> Yup, hasn't been forgotten https://github.com/apache/airflow/issues/51552 :) Yeah - but you can't solve the knot "partially" if you do not know how you are going to solve #51552. Just to show you how I imagine the target architecture (simplified dependency tree): ``` * triggerer - common - task-sdk * dag processor - common - task-sdk * scheduler - common - executors (all of them potentially * api_server - common * celery_executor - common (including executor base) - celery.common * kubernetes.executor - kubernetes.common - common (including executor base) * kubernetes.provider (implements worker) - kubernetes.common - task.sdk * celery_provider (implements worker) - celery.common - task.sdk ``` Each of those distributions will use a subset of things from commmon (and use optional extras from common as dependency for things it uses (for example executors will depend on "common[executor]" etc. I believe this is the target setup we should have and if we can agree to it, we might define first and second and third step how to get there. But we need to agree where we are going first. It cannot be done incrementally to design the final architecture without imagining final setup. -- 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]
