Generated banner for Managed Airflow Migrations
Generated logo for Managed Airflow Migrations

Managed Airflow Migrations

GoogleOfficialPublished by Google

  • Skill
  • Workflow
  • Cloud and DevOps
  • Apache-2.0
  • No issues found

From the author

Provides guidance for migrating Apache Airflow DAGs in Managed Service for Apache Airflow (MSAA; formerly Cloud Composer). Covers migration to Airflow 2.11.1 (MSAA Gen 2 and 3) and Airflow 3 (MSAA Gen 3), including environment inspection, GCS download/upload and scanning patterns for breaking changes. Use when migrating the DAG code to newer Airflow version. Don't use when checking DAG run failures unrelated to code migration.
— the description by Google

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill assists developers in migrating Apache Airflow DAGs from existing Managed Service for Apache Airflow environments to Airflow 2.11.1 or Airflow 3. It provides a systematic approach including environment inspection, dependency mapping, code scanning for breaking changes, and deployment verification. The skill covers specific remediation steps for provider package updates, core Airflow changes, and deprecated features, ensuring compatibility with the target environment.

What it does

  • Guides the inspection and download of existing DAG files from Managed Service for Apache Airflow environments.
  • Maps dependency version progressions for Google, SSH, and HTTP providers.
  • Provides scan commands to identify breaking changes in DAG code, such as deprecated operators and API changes.
  • Offers remediation steps for upgrading to Airflow 2.11.1 and Airflow 3.
  • Facilitates deployment of migrated DAGs to target GCS buckets.
  • Supports verification of migrated DAGs using Airflow CLI and Cloud Logging.

When to use it

  • When planning to migrate existing DAGs to Airflow 2.11.1 or Airflow 3 in Managed Service for Apache Airflow.
  • When identifying necessary code changes due to provider package upgrades.
  • When refactoring legacy DAG features like SubDAGs or SLAs for newer Airflow versions.
  • When verifying the successful registration and parsing of migrated DAGs in a target environment.

Advantages

  • Provides a clear, phased approach to complex Airflow version migrations.
  • Includes specific grep-based scan patterns to quickly locate code requiring updates.
  • Offers actionable remediation advice for common breaking changes.
  • Ensures consistent deployment and verification practices using standard CLI tools.

Usage examples

“How do I identify if my DAGs use operators that were removed in recent Google provider versions?”
The agent will provide specific grep commands to scan your local DAG directory for deprecated operators like BigQueryExecuteQueryOperator or AutoML operators.
“I am migrating to Airflow 3. What changes do I need to make to my imports?”
The agent will guide you through updating imports to the decoupled Airflow SDK and standard provider bundles, such as changing airflow.DAG to airflow.sdk.DAG.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/google/managed-airflow-migrations/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip managed-airflow-migrations.zip -d .agents/skills

Documentation by Google

Managed Service for Apache Airflow (formerly Cloud Composer) Migration Guide

This skill guides you through the process of adjusting Airflow DAGs from an existing Managed Service for Apache Airflow (formerly Cloud Composer) environment (or available locally) to make them compatible with Airflow 2.11.1 (MSAA Gen 2 or 3) or Airflow 3 (MSAA Gen 3).


Attribution

MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:managed-airflow-migrations)" and append agent-skills/1.0 (skill:managed-airflow-migrations) to User-Agent headers.

Phase 1: Discovery & Download

Before making any changes, download the existing DAG files if explicitly requested. Inspect the source environment to confirm source version only if explicitly requested. For detailed instructions about environment inspection and downloading files check references/environment-inspection.md.


Phase 2: Target Version & Dependency Mapping

2.1 Airflow 2.11.1+ Dependency Mapping

If migrating to Airflow 2.11.1 (MSAA Gen 2) or Airflow 3, use the list below to trace the version progression of key dependencies. The list covers changes needed to get to Airflow 2.11.1. Take them into account when migrating from Airflow 2 (earlier than 2.11.1) to Airflow 3.

Composer 2.10.0 (Airflow 2.10.2)
  • Google Provider: 10.26.0

  • SSH Provider: 3.14.0

  • HTTP Provider: 4.13.3

  • Breaking Changes: Baseline for oldest fully documented source.

Composer 2.15.3 (Airflow 2.10.5)
  • Google Provider: 18.0.0

  • SSH Provider: 4.1.4

  • HTTP Provider: 5.3.4

  • Breaking Changes:

    • SSH Provider 4.0.0: Hook timeout removed; get_conn() context manager.

    • HTTP Provider 5.0.0: SimpleHttpOperator -> HttpOperator.

    • Google Provider 11.0.0: BigQueryExecuteQueryOperator removed.

    • Google Provider 12.0.0: Legacy Data Pipeline operators removed.

    • Google Provider 13.0.0: AutoMLBatchPredictOperator removed.

    • Google Provider 17.0.0: BigQueryCreateEmptyTableOperator and BigQueryCreateExternalTableOperator removed; Life Sciences operators removed.

    • Google Provider 18.0.0: Legacy DV360 operators removed.

Composer 2.16.1 (Airflow 2.10.5)
  • Google Provider: 19.0.0

  • SSH Provider: 4.1.6

  • HTTP Provider: 5.5.0

  • Breaking Changes: Google Provider 19.0.0: AutoML operators removed (use Vertex AI).

Composer 2.17.0 (Target Airflow 2.11.1)
  • Google Provider: 20.0.0

  • SSH Provider: 5.0.0

  • HTTP Provider: 6.0.2

  • Breaking Changes:

    • SSH Provider 5.0.0: sshtunnel removed (native tunneling).

    • HTTP Provider 6.0.0: JSON serialization.

    • Google Provider 20.0.0: ADLS Gen2 migration.

2.2 Airflow 3 Migration

If migrating to Airflow 3 (MSAA Gen 3), note that this is a major version upgrade with significant changes, including:

  • Decoupled Task SDK (imports change from airflow to airflow.sdk).

  • Removal of direct metadata DB access.

  • Renaming of Dataset to Asset.

  • Removal of SubDAGs and SLAs.

  • Changes to context variables availability.

Take into account all applicable changes within Airflow 2 (e.g. when migrating from Airflow 2.10.2, apply changes needed to move to Airflow 2.11.1 and Airflow 3 migration changes on top of that).


Phase 3: Analysis & Remediation (Scanning Downloaded Files)

Run the scan commands from the root of your local workspace (./migration_workspace unless indicated otherwise).


3.1 Airflow 2.11.1 Core & Dependency checks

Use these scans if migrating to Airflow 2.11.1+ (intermediate step when migrating to Airflow 3).

3.1.1 Dataset Scheduling (Airflow 2.11.0)
  • Change: DAGs scheduled on datasets only trigger if events occur while the DAG is unpaused.

  • Scan Command: grep -rn "Dataset(" ./dags

  • Remediation: You MUST document that these DAGs must remain unpaused to catch events, or plan manual triggers for catch-up.

3.1.2 HTML in Descriptions (Airflow 2.11.0)
  • Change: Raw HTML in DAG docs / params is escaped by default.

  • Scan Command:

    grep -rn -E "doc_md.*<|doc_md.*>|description.*<|description.*>" ./dags
  • Remediation: Convert HTML to Markdown, or set AIRFLOW__WEBSERVER__ALLOW_RAW_HTML_DESCRIPTIONS=True in target.

3.1.3 Teardown Tasks (Airflow 2.10.5)
  • Change: Teardowns always run when a DAG is marked failed.

  • Scan Command: grep -rn "as_teardown" ./dags

  • Remediation: Ensure teardown tasks are idempotent.

3.1.4 Pendulum 3 Upgrade (Airflow 2.11.0)
  • Change: Period renamed to Interval, testing helpers removed.

  • Scan Command (Code):

    grep -rn -E "pendulum\.Period|pendulum\.period" ./dags
  • Scan Command (Tests):

    grep -rn -E "\.test\(|set_test_now\(" ./tests 2>/dev/null || true
  • Remediation: Replace Period with Interval, and period(...) with interval(...).


3.2 Path A: Airflow 2.11.1 Provider Package Scan
3.2.1 SSH Provider (SSH 4.0.0 & 5.0.0)
  • Scan Command (Timeout): grep -rn "SSHHook" ./dags | grep "timeout"

  • Scan Command (Context Manager): grep -rn "with SSHHook" ./dags

  • Scan Command (Tunnel Attributes): grep -rn "\.get_tunnel" ./dags

  • Remediation:

    • Replace timeout with conn_timeout in SSHHook.

    • Replace with hook as conn: with with hook.get_conn() as conn:.

    • Use get_tunnel() as context manager: with hook.get_tunnel(...) as tunnel:.

3.2.2 HTTP Provider (HTTP 5.0.0 & 6.0.0)
  • Scan Command: grep -rn "SimpleHttpOperator" ./dags

  • Remediation: Replace SimpleHttpOperator with HttpOperator.

3.2.3 Google Provider (v11 to v20)
  • Scan Command (BigQuery query):

    grep -rn "BigQueryExecuteQueryOperator" ./dags
    • Remediation: Replace with BigQueryInsertJobOperator (use configuration dict).

  • Scan Command (BigQuery table):

    grep -rn -E "BigQueryCreateEmptyTableOperator|BigQueryCreateExternalTableOperator" ./dags
    • Remediation: Replace with BigQueryCreateTableOperator (use table_resource dict).

  • Scan Command (AutoML):

    grep -rn -E "AutoMLTrainModelOperator|AutoMLPredictOperator|AutoMLCreateDatasetOperator|AutoMLBatchPredictOperator" ./dags
    • Remediation: Migrate to Vertex AI operators.

  • Scan Command (Dataflow):

    grep -rn -E "CreateDataPipelineOperator|RunDataPipelineOperator" ./dags
    • Remediation: Replace with DataflowCreatePipelineOperator/DataflowRunPipelineOperator.

  • Scan Command (Life Sciences):

    grep -rn "LifeSciencesRunPipelineOperator" ./dags`
    • Remediation: Migrate to Google Cloud Batch operators (BatchCreateJobOperator).

  • Scan Command (ADLS to GCS): grep -rn "ADLSToGCSOperator" ./dags

    • Remediation: Ensure file_system_name is provided.


3.3 Airflow 3 Migration checks

Use instructions from references/airflow-3.md when migrating to Airflow 3.


Phase 4: Deployment & Verification

Perform deployment and verification steps only if explicitly requested to do so.

4.1 Static Verification (when migrating to Airflow 3)

After applying code changes for Airflow 3, verify syntax correctness. If available in the development environment, run static lint checks:

ruff check {target_dag_file} --select AIR30

Resolve any reported deprecation warnings before finalization. If ruff is not available, recommend installing one.

4.2 Deployment to MSAA
4.2.1 Get Target GCS Bucket Path (only when requested)
gcloud composer environments describe <TARGET_ENV> \
    --location <TARGET_REGION> \
    --format="value(config.dagGcsPrefix)"

Expected Output: gs://<target-bucket-name>/dags

4.2 Upload Modified DAGs and Bucket Dependencies (Only when requested)

Perform this step only if explicitly requested to do so. Copy the modified DAGs and any backed-up bucket dependencies from your local workspace to the target GCS bucket. If you skipped the inspection step, ensure you have the correct <target-bucket-name>.

  1. Upload DAGs:

    gcloud storage cp -r ./dags/* gs://<target-bucket-name>/dags/
  2. Upload Other Bucket Dependencies (If applicable):

    gcloud storage cp -r ./migration_workspace/<dependency-folder> gs://<target-bucket-name>/<dependency-folder>
4.3 Verify DAGs via Airflow CLI

Perform this step only if explicitly requested to upload modified DAGS to a target environment (and after uploading).

You can verify that your DAGs have been successfully uploaded, parsed, and registered by the Airflow scheduler in the target environment using the Airflow CLI.

  1. List Registered DAGs: Run the following command to list all DAGs registered in the target environment. Verify that your migrated DAGs appear in this list.

    gcloud composer environments run <TARGET_ENV> \
        --location <TARGET_REGION> \
        dags list
  2. Check for Import Errors: If some DAGs are missing from the list, or to ensure there are no parsing issues, check for import errors:

    gcloud composer environments run <TARGET_ENV> \
        --location <TARGET_REGION> \
        dags list-import-errors

    Expected Output:

    • If there are no errors, the command will output No data found.

    • If there are errors, it will list the file path and the traceback of the error.

Note: It may take a couple of minutes for the Airflow scheduler to parse the new files and for changes to reflect in these commands.

4.4 Verify in Cloud Logging

Perform this step only if explicitly requested to upload modified DAGS to a target environment (and after uploading). Monitor Cloud Logging for the target environment to detect any runtime errors or import errors.

Run the following query in the GCP Cloud Logging Console (or via gcloud logging read):

resource.type="cloud_composer_environment"
resource.labels.environment_name="<TARGET_ENV>"
log_id("airflow-scheduler")
severity>=ERROR

Appendix: Local Environment Verification

If you want to verify your changes locally before deploying to the target environment, you can use the Composer Local Development CLI tool (composer-dev). Use references/local-development-environment.md as a reference for interactions with local development environments.

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs a command-line tool

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Google
Publisher
Google (Official)
Source
google/skills · skills/cloud/managed-airflow-migrations · commit 2194d3b
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google or Google.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download managed-airflow-migrations.zip