Body

I’ve been working on splitting SDK usages in Airflow Core (and vice versa, but removing SDK from Core is the current priority), see #52141. Most of the work is close to done, but I’m having some trouble isolating DeadlineAlert and related types. I’m hesitant to start working on them since development is still quite active around them and want to recruit some help from people more familiar with the progress.

Reading existing implementation I think we need to

1. Create Core-only deadline and callback types that are used in scheduler etc. These should live in airflow.serialization.definitions.
2. Move serialization to airflow.serialization.encoders.
3. Move deserialization to airflow.serialization.decoders; this can’t reference SDK types.
4. Remove airflow.models.deadline references in SDK. We should change DeadlineReference declarations to not use ReferenceModels, and create SerializedDeadlineReference types in the scheduler to reference ReferenceModels.
5. ReferenceModels should be moved out of airflow.models to ``airflow.serialization.definitions`.

I’m not entirely familiar to the current code structure and may be missing something. I’m also not sure if there are other plans to change those types and functions that may affect this. Please feel free to provide inputs on this @ferruzzi @ramitkataria (please also tag others involved).

Committer

• I acknowledge that I am a maintainer/committer of the Apache Airflow project.