Managed Airflow Gen 3 development mode and hibernation GA, upgrade rollbacks added

Development mode environments and Environment hibernation are now generally available (GA).

You can now create Managed Airflow (Gen 3) environments with Airflow 3 in development mode to test and develop DAGs before publishing them to production. You can hibernate development mode environments when you no longer need them. Hibernation reduces most environment costs to zero.

Upgrade rollbacks are available in Managed Airflow (Gen 3). You can roll back an environment upgrade if you encounter degraded performance, Airflow bugs, or compatibility issues with your DAGs, plugins, or dependencies.

This feature is gradually rolling out over several releases. In this release, it's available in the following regions: europe-north1, europe-west3, us-east1, and us-west2.

New Managed Airflow (Gen 3) environments created while the Restrict Endpoint Usage (constraints/gcp.restrictEndpointUsage) organization policy is active now use regional endpoints for services like Cloud Storage, Cloud Logging, Pub/Sub, and Data Lineage.

(Managed Airflow Gen 3) Added the scheduler loop duration metric:

• composer.googleapis.com/workload/scheduler/loop_duration: time spent running one Scheduler loop.

Database retention in Managed Airflow (Gen 3) now includes new Airflow 3 metadata tables, and updated retention logs to report the exact number of removed rows.

This feature is gradually rolling out over several releases. In this release, it's available in the following regions: europe-north1, europe-west3, us-east1, and us-west2.