Hi, AIP-85 <https://cwiki.apache.org/confluence/x/_Q7OEg> was modified to include only the *DAG importer* context from the design doc, and AIP-110 <https://cwiki.apache.org/confluence/x/boCnGQ> was created for the interactive DAG processor(original AIP-85: Track 2).
On Sun, May 10, 2026 at 2:26 PM Igor Kholopov <[email protected]> wrote: > ---------- Forwarded message --------- > From: Dilnaz Amanzholova <[email protected]> > Date: Fri, May 8, 2026 at 4:59 PM > Subject: [DISCUSS] New AIP-XX: AIP-85-1: DAG importer > > > Dear Airflow Community, > > I would like to start a discussion regarding AIP-85-1: DAG importer. > > To clarify, this is not a new proposal but a scoped-down, modular part of > the existing AIP-85. Original AIP-85 was created in 2024, and since then, > Airflow 3 has developed new integral functionalities (like already > implemented AIP-66 and AIP-72). We decided to divide the parent AIP into > two independent parts to better manage complexity. While AIP-85 covers the > overarching architectural framework for parsing controls, this specific > part (AIP-85-1) focuses strictly on implementing the DAG importer and its > configuration. > > The goal is to allow alternative formats like YAML to be first-class > citizens in Airflow by decoupling DAG discovery from parsing. This modular > approach will allow us to implement the core importer mechanism faster and > independently of broader architectural updates. > > NOTE: There is an ongoing discussion around AIP-108, which is proposing > coordinator for DAG parsing and they are slightly overlapping. I think they > need to be aligned. > > Please see the attached discussion document for your reference: link > <https://docs.google.com/document/d/1K6-4cGoZItXGQHZjOydNbc7rGtOp_XKfFurMnFptKe0/edit?usp=sharing> > > I look forward to your feedback. > > Kind regards, > Dilnaz Amanzholova > >
