What problem does it solve?
Upgrading Apache Airflow DAGs to newer versions on Managed Service for Apache Airflow (formerly Cloud Composer) involves tracking dozens of breaking changes across core Airflow and provider packages, and missing one causes DAG import failures after deployment.
Core Features & Use Cases
- Dependency Mapping: Traces breaking changes across Composer versions and Google, SSH, and HTTP provider releases up to Airflow 2.11.1 and Airflow 3.
- Scan-and-Remediate Workflow: Provides grep-based scan commands to detect deprecated operators, imports, context variables, SubDAGs, and SLAs, paired with concrete remediation steps.
- Deployment & Verification: Covers GCS upload of migrated DAGs, Airflow CLI import-error checks, Cloud Logging queries, and local verification with the composer-dev CLI.
- Use Case: A data engineer migrating a Composer 2.10 environment to Airflow 3 scans their DAGs, replaces removed operators like BigQueryExecuteQueryOperator, updates imports to airflow.sdk, and verifies the DAGs parse without import errors.
Quick Start
Migrate my Airflow DAGs in this workspace to Airflow 3 on Managed Service for Apache Airflow and scan them for breaking changes.