On one side it makes sense to me, and I actually like the thinking "providers
should only be for DAG authors". That makes it simple to figure whether
something should belong to providers. If we go that way then FAB would no
longer be a provider but a plugin which would be one step closer to not
A sortof third option...
Seems there could be good reason to release executor separately
e.g.
`apache-airflow-providers-aws-executors`
Separate from the dag authoring stuff. So e.g. with cncf you could stick
with old dag authoring stuff but stay on latest k8s executor.
On Mon, Sep 16, 2024 at
Hi all,
yes, diverged a bit. I'll add an agenda item for the next Airflow 3 dev
call.
Main question as outcome would be: Shall we split the Providers if we
are (ongoing) also planning to split the deployment dependencies of
Scheduler, Worker, Webserver etc?
-->
https://cwiki.apache.org/confluen
