Re: Naming things: What should the imports in dag files for DAG etc. be?

2024-08-31 Thread Jarek Potiuk
Should be: ``` @configure_settings @configure_worker_plugins def cli_worker(): pass ``` On Sun, Sep 1, 2024 at 12:05 AM Jarek Potiuk wrote: > Personally for me "airflow.sdk" is best and very straightforward. And we > have not yet used that for other things before, so it's free to use. > > "

Re: Naming things: What should the imports in dag files for DAG etc. be?

2024-08-31 Thread Jens Scheffler
Hi Ash, I was thinking hard... was setting the email aside and still have no real _good_ ideas. I am still good with "models" and "sdk". Actually what we want to define is an "execution interface" to which the structual model as API in Python/or other language gives bindings and helper methods.

Re: Naming things: What should the imports in dag files for DAG etc. be?

2024-08-31 Thread Jarek Potiuk
Personally for me "airflow.sdk" is best and very straightforward. And we have not yet used that for other things before, so it's free to use. "Models" and similar carried more (often misleading) information - they were sometimes database models, sometimes they were not. This caused a lot of confus