capabilities.work

Onboard a DAG

A 5-step recipe with Apache Airflow. We can help you get access.

Recipe · 5 steps

Onboard a DAG

with Apache Airflow

Assemble a complete read-only briefing on a single DAG.

  1. Read the DAG record for its owners, tags, paused state, and the file_token that authorizes fetching its source in a later step.
  2. Read the extended DAG details for the timetable description, concurrency limits, catchup posture, start date, and default arguments — the fields that explain how the DAG actually behaves.
  3. List the DAG's tasks to see the graph: each task id, its operator class, its downstream ids, its pool, and its retry posture.
  4. Fetch the DAG's Python source using the file_token from the DAG record. The token is a signed reference to the file path rather than the path itself, which is why the source cannot be requested by filename.
  5. Pull the most recent DAG runs, newest first, so the caller can judge whether this pipeline has been finishing cleanly before depending on it.
What you'll need to have ready
  • dagId: The DAG identifier to profile.
  • runLimit: How many recent DAG runs to pull for the reliability check. Defaults to 25 when omitted.
For your developer

Arazzo workflow apache-airflow:onboard-dag, 5 operations: getApiV2DagsByDagId → getApiV2DagsByDagIdDetails → get_tasks → get_dag_source → getApiV2DagsByDagIdDagRuns. Specs on APIs.io.

More recipes with Apache Airflow

Audit DAG Runs Across the FleetCollect DAG Run Results from XComTrace Dataset-Driven LineageDeployment Preflight CheckDiagnose a Failed DAG RunForce a Task Instance StateProvision a User with a RoleRegister a Connection After Testing ItRetry Failed Tasks in a DAG RunTrigger a DAG Run and Wait for Completion