Delete Managed Airflow environments

Managed Airflow (Gen 3) | Managed Airflow (Gen 2) | Managed Airflow (Legacy Gen 1)

This page explains how to delete your Managed Airflow environment.

Resources that are not deleted automatically

Deleting your environment does not delete the following data in your project:

• Your environment's Cloud Storage bucket.
• Cloud Logging logs.

To avoid incurring charges to your Google Cloud account, export your data and delete the environment's bucket and Cloud Logging logs, as needed.

Note: As an alternative, you can reuse your environment's bucket by specifying it as a custom bucket for a new environment. For example, you can do so to preserve existing policies or CI/CD integrations.

If you use alerting policies to monitor your environment's metrics, delete these policies before deleting your environment.

Your environment's cluster is deleted automatically

Warning: Do not delete the GKE cluster of your environment manually. This happens automatically during the environment deletion. If you delete the cluster before the environment, then attempting to delete your environment results in an error. To fix this problem, see Troubleshooting.

Delete a Managed Airflow environment

Console

1. Delete the Managed Airflow environment:

   1. In the Google Cloud console, go to the Environments page.

      Go to Environments

   2. Select your environment and click Delete.

   3. Wait until the environment is deleted.

2. Delete your environment's bucket. Managed Airflow does not delete the environment's bucket automatically.

   Warning: Deleting your environment's bucket deletes all objects stored within the bucket, such as DAGs and plugins. You might not be able to recover these objects, depending on the bucket's settings and the length of time since the bucket was deleted.

   1. In the Google Cloud console, go to the Storage > Browser page.

      Go to Storage > Browser

   2. Select the environment's bucket and click Delete. For example, this bucket can be named us-central1-example-environ-c1616fe8-bucket.

gcloud

1. Delete the Managed Airflow environment:

   gcloud composer environments delete ENVIRONMENT_NAME \
       --location LOCATION
   

   Replace:

   • ENVIRONMENT_NAME with the name of the environment.
   • LOCATION with the region where the environment is located.

2. Delete your environment's bucket. Managed Airflow does not delete the environment's bucket automatically.

   Warning: Deleting your environment's bucket deletes all objects stored within the bucket, such as DAGs and plugins. You might not be able to recover these objects, depending on the bucket's settings and the length of time since the bucket was deleted.

   gcloud storage rm gs://BUCKET_NAME --recursive
   

   Replace:

   • BUCKET_NAME with the name of your environment's bucket. For example, this bucket can be named us-central1-example-environ-c1616fe8-bucket.

API

To delete an environment, construct an environments.delete API request with the environment ID.

Caution: Managed Airflow doesn't automatically delete the environment's bucket. If it's no longer needed, delete it manually.

Terraform

To delete an environment using Terraform, remove the Managed Airflow configuration from your overall resource configuration and run terraform apply.

Caution: Managed Airflow does not automatically delete the environment's bucket. If it's no longer needed, delete it manually.

What's next

• Create environments
• Enable and disable Managed Airflow service