> On 30 Aug 2024, at 17:48, Ash Berlin-Taylor <a...@apache.org> wrote:
>
> Where should DAG, TaskGroup, Labels, decorators etc for authoring be imported
> from inside the DAG files? Similarly for DagRun, TaskInstance (these two
> likely won’t be created directly by users, but just used for reference
> docs/type hints)
>
How about airflow.definitions? When discussing assets there’s a question raised
on how we should call “DAG files” going forward (because those files now may
not contain user-defined DAGs at all). “Definition files” was raised as a
choice, but there’s no existing usage and it might be a bit to catch on. If we
put all these things into airflow.definitions, maybe people will start using
that term?
As a side note, I wonder if we should do the user-internal separation better
for DagRun and TaskInstance. We already have that separation for DAG/DagModel,
Dataset/DatasetModel, and more. Maybe we should also have constructs that users
only see, and are converted to “real” objects (i.e. exists in the db) for the
scheduler. We already sort of have those in DagRunPydantic and
TaskInstancePydantic, we just need to name them better and expose them at the
right places.
TP
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org
