> On 16 Sep 2025, at 08:58, asquator <asqua...@proton.me> wrote:
>
> Yes, exposing pluggable features means fixing an API, which is confining and
> just hard to do given the current implementation
class MyScheduler:
def execute(self):
while True:
# Do what ever you want.
`airflow scheduler --impl=my.module.MyScheduler`
That is the API.
That is as pluggable as we need it to be.
Everything can be built on top of that, including if you want it, a pluggable
task selection mechanisms.
Airflow already has too many config options and ways of tuning behaviour. We
need less of them, not more.
