Managed Service for Apache Airflow: API Dependencies Updated
Several API dependencies are being phased out for Managed Airflow (Gen 3) and will require separate enablement for new Gen 2 environments. This change impacts users creating new Gen 2 environments in projects where the Cloud Composer API was not previously enabled. Existing environments remain unaffected, but users provisioning new Gen 2 environments, especially via automation, must now explicitly enable these dependencies.
Enhancements (1) ›
- Managed Service for Apache Airflow
Several API dependencies that aren't required by Managed Airflow (Gen 3) are now phased out and must be enabled separately if you want to create Managed Airflow (Gen 2) environments in a new project. This change was announced previously . The following API dependencies were phased out: artifactregistry.googleapis.com cloudbuild.googleapis.com container.googleapis.com pubsub.googleapis.com The following API dependencies aren't phased out yet and are scheduled to be detached from the Cloud Composer API in the future: sqladmin.googleapis.com Existing Managed Airflow (Gen 3) and Managed Airflow (G
https://docs.cloud.google.com/release-notes#June_08_2026
Related releases
- Managed Service for Apache Airflow: New Release and Deprecations Google Cloud release notes ·
- Cloud SDK 578.0.0: Database Migration default change, AlloyDB backup DR GA, BigQuery improvements Google Cloud release notes ·
- Checkout.com Migrates to Managed Airflow on GCP for Reliability and Cost Savings Google Cloud Blog ·
- Checkout.com Migrates to Google Cloud Composer 3 for Improved Data Orchestration Google Cloud Blog ·
- Managed Airflow Gen 3 supports internal-only Cloud Run endpoints Google Cloud release notes ·
- Cloud Composer: Internal ingress for Cloud Run endpoints Google Cloud release notes ·