Le 15 septembre 2026, tous les environnements Cloud Composer 1 et Cloud Composer 2 version 2.0.x atteindront leur fin de vie prévue et vous ne pourrez plus les utiliser. Nous vous recommandons de planifier la migration vers Cloud Composer 3.
Cette page explique comment supprimer votre environnement Cloud Composer.
Ressources qui ne sont pas supprimées automatiquement
La suppression de votre environnement ne supprime pas les données suivantes de votre projet :
Bucket Cloud Storage de votre environnement.
Journaux Cloud Logging.
Pour éviter que des frais ne soient facturés sur votre compte Google Cloud , exportez vos données et supprimez le bucket de l'environnement ainsi que les journaux Cloud Logging, si nécessaire.
Si vous utilisez des règles d'alerte pour surveiller les métriques de votre environnement, supprimez-les avant de supprimer votre environnement.
Le cluster de votre environnement est supprimé automatiquement.
Supprimer un environnement Cloud Composer
Console
Supprimez l'environnement Cloud Composer.
Dans la console Google Cloud , accédez à la page Environnements.
Sélectionnez le bucket de l'environnement, puis cliquez sur Supprimer. Par exemple, ce bucket peut être nommé us-central1-example-environ-c1616fe8-bucket.
LOCATION par la région dans laquelle se trouve l'environnement.
Supprimez le bucket de votre environnement. Cloud Composer ne supprime pas automatiquement le bucket de l'environnement.
gcloudstoragermgs://BUCKET_NAME--recursive
Remplacez :
BUCKET_NAME par le nom du bucket de votre environnement. Par exemple, ce bucket peut être nommé us-central1-example-environ-c1616fe8-bucket.
API
Pour supprimer un environnement, rédigez une requête API environments.delete avec l'ID de l'environnement.
Terraform
Pour supprimer un environnement à l'aide de Terraform, supprimez la configuration Cloud Composer de votre configuration globale de ressources et exécutez terraform apply.
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2025/09/03 (UTC).
[[["Facile à comprendre","easyToUnderstand","thumb-up"],["J'ai pu résoudre mon problème","solvedMyProblem","thumb-up"],["Autre","otherUp","thumb-up"]],[["Difficile à comprendre","hardToUnderstand","thumb-down"],["Informations ou exemple de code incorrects","incorrectInformationOrSampleCode","thumb-down"],["Il n'y a pas l'information/les exemples dont j'ai besoin","missingTheInformationSamplesINeed","thumb-down"],["Problème de traduction","translationIssue","thumb-down"],["Autre","otherDown","thumb-down"]],["Dernière mise à jour le 2025/09/03 (UTC)."],[[["\u003cp\u003eDeleting a Cloud Composer environment does not automatically delete the associated Cloud Storage bucket or Cloud Logging logs, which may need to be manually deleted to avoid charges.\u003c/p\u003e\n"],["\u003cp\u003eIt is crucial to delete any alerting policies tied to your environment before deleting the environment itself.\u003c/p\u003e\n"],["\u003cp\u003eThe environment's GKE cluster is automatically deleted during the environment deletion process, and attempting to manually delete it beforehand will result in errors.\u003c/p\u003e\n"],["\u003cp\u003eAfter deleting the environment, users must also delete the associated Cloud Storage bucket manually via the console, gcloud or API, if it is no longer needed.\u003c/p\u003e\n"],["\u003cp\u003eDeleting the environment's bucket will permanently remove all data stored within it, including DAGs and plugins.\u003c/p\u003e\n"]]],[],null,["\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\n[Cloud Composer 3](/composer/docs/composer-3/delete-environments \"View this page for Cloud Composer 3\") \\| [Cloud Composer 2](/composer/docs/composer-2/delete-environments \"View this page for Cloud Composer 2\") \\| **Cloud Composer 1**\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page explains how to delete your Cloud Composer environment.\n\nResources that are not deleted automatically\n\nDeleting your environment does not delete the following data in your project:\n\n- Your environment's Cloud Storage bucket.\n- Cloud Logging logs.\n\nTo avoid incurring charges to your Google Cloud account, export your\ndata and [delete the environment's bucket](/storage/docs/deleting-buckets)\nand Cloud Logging logs, as needed.\n\nIf you use [alerting policies](/monitoring/alerts/manage-alerts) to monitor your\nenvironment's metrics, delete these policies before deleting your environment.\n\nYour 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](/composer/docs/composer-1/known-issues#deleted-cluster).\n\nDelete a Cloud Composer environment \n\nConsole\n\n1. Delete the Cloud Composer environment:\n\n 1. In the Google Cloud console, go to the **Environments** page.\n\n [Go to Environments](https://console.cloud.google.com/composer/environments)\n 2. Select your environment and click **Delete**.\n\n 3. Wait until the environment is deleted.\n\n2. Delete your environment's bucket. Cloud Composer\n does not delete the environment's bucket automatically.\n\n | **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](/storage/docs/soft-delete) and the length of time since the bucket was deleted.\n 1. In the Google Cloud console, go to the **Storage** \\\u003e\n **Browser** page.\n\n [Go to Storage \\\u003e Browser](https://console.cloud.google.com/storage/browser)\n 2. Select the environment's bucket and click **Delete** . For example, this\n bucket can be named `us-central1-example-environ-c1616fe8-bucket`.\n\ngcloud\n\n1. Delete the Cloud Composer environment:\n\n gcloud composer environments delete \u003cvar translate=\"no\"\u003eENVIRONMENT_NAME\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e\n\n Replace:\n - `ENVIRONMENT_NAME` with the name of the environment.\n - `LOCATION` with the region where the environment is located.\n2. Delete your environment's bucket. Cloud Composer\n does not delete the environment's bucket automatically.\n\n **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](/storage/docs/soft-delete) and the length of time since the bucket was deleted. \n\n gcloud storage rm gs://\u003cvar translate=\"no\"\u003eBUCKET_NAME\u003c/var\u003e --recursive\n\n Replace:\n - `BUCKET_NAME` with the name of your environment's bucket. For example, this bucket can be named `us-central1-example-environ-c1616fe8-bucket`.\n\nAPI\n\nTo delete an environment, construct an [`environments.delete`](/composer/docs/reference/rest/v1/projects.locations.environments/delete)\nAPI request with the environment ID.\n| **Caution:** Cloud Composer doesn't automatically delete the environment's bucket. If it's no longer needed, delete it manually.\n\nTerraform\n\nTo delete an environment using Terraform, remove the\nCloud Composer configuration from your overall resource\nconfiguration and run `terraform apply`.\n| **Caution:** Cloud Composer does not automatically delete the environment's bucket. If it's no longer needed, delete it manually.\n\nWhat's next\n\n- [Create environments](/composer/docs/composer-1/create-environments)\n- [Enable and disable Cloud Composer service](/composer/docs/composer-1/enable-composer-service)"]]
