Deployment Preflight Check

Deployment Preflight Check

Gate on Airflow health, then report import errors and DAG warnings.

1. Require both the metadatabase and the scheduler to report healthy. A scheduler whose latest heartbeat has gone stale reports unhealthy here, which is the single most useful signal that queued tasks will never start.
2. Capture the running Airflow version and git build so the deployment record states exactly what is serving traffic.
3. List DAG files that failed to parse. This is the check a health endpoint cannot make: a DAG with a syntax or import error never registers, so it does not appear as broken — it simply is not there.
4. List DAG warnings, such as a DAG referencing a pool that does not exist. Note that this collection returns its items under an "import_errors" property rather than a warnings-specific name — an upstream quirk of the Airflow OpenAPI descripti
5. Count the active DAGs the deployment is serving, giving the preflight a concrete number to compare against the expected inventory.

What you'll need to have ready

• errorLimit: How many import errors to return. Defaults to 100 when omitted.

For your developer

Arazzo workflow apache-airflow:deployment-preflight, 5 operations: get_health → get_version → get_import_errors → get_dag_warnings → getApiV2Dags. Specs on APIs.io.