In diesem Thema wird erläutert, wie Umgebungen in Apigee Hybrid gelöscht werden. Weitere Informationen finden Sie unter Umgebungen und Umgebungsgruppen.
So löschen Sie eine Umgebung
Angenommen, Sie haben zwei Umgebungen test und prod. Die Definitionen in der Überschreibungendatei könnten in etwa so aussehen:
Wenn der Probelauf fehlerfrei ist, entfernen Sie die Laufzeitkomponenten:
helm delete $ENV_NAME -n apigee
Öffnen Sie die Überschreibungsdatei und entfernen Sie die prod-Umgebungsdefinition aus envs und virtualhosts. Behalten Sie nur die test-Definitionen bei. Beispiel:
[[["Leicht verständlich","easyToUnderstand","thumb-up"],["Mein Problem wurde gelöst","solvedMyProblem","thumb-up"],["Sonstiges","otherUp","thumb-up"]],[["Schwer verständlich","hardToUnderstand","thumb-down"],["Informationen oder Beispielcode falsch","incorrectInformationOrSampleCode","thumb-down"],["Benötigte Informationen/Beispiele nicht gefunden","missingTheInformationSamplesINeed","thumb-down"],["Problem mit der Übersetzung","translationIssue","thumb-down"],["Sonstiges","otherDown","thumb-down"]],["Zuletzt aktualisiert: 2025-09-04 (UTC)."],[[["\u003cp\u003eThis document outlines the process for deleting an environment in Apigee hybrid, using the example of removing a "prod" environment while retaining a "test" environment.\u003c/p\u003e\n"],["\u003cp\u003eDeleting an environment involves removing it from any associated environment groups using specific \u003ccode\u003ecurl\u003c/code\u003e commands, adjusting the command depending on your data residency requirements.\u003c/p\u003e\n"],["\u003cp\u003eA dry run using \u003ccode\u003ehelm delete\u003c/code\u003e with the \u003ccode\u003e--dry-run\u003c/code\u003e flag is recommended to test the removal of runtime components before proceeding with actual removal.\u003c/p\u003e\n"],["\u003cp\u003eAfter the runtime components are deleted, the corresponding environment definition needs to be manually removed from the \u003ccode\u003eenvs\u003c/code\u003e and \u003ccode\u003evirtualhosts\u003c/code\u003e sections within the overrides file.\u003c/p\u003e\n"],["\u003cp\u003eThe steps include using \u003ccode\u003egcloud\u003c/code\u003e for authentication, and executing \u003ccode\u003ehelm delete\u003c/code\u003e to remove runtime components.\u003c/p\u003e\n"]]],[],null,["# Delete environments\n\n| You are currently viewing version 1.12 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\n\nThis topic explains how to delete environments in Apigee hybrid. See also\n[About environments and environment groups](/apigee/docs/api-platform/fundamentals/environments-overview).\n\nHow to delete an environment\n----------------------------\n\nAssume that you have two environments, **test** and **prod**. In\nyour overrides file, the definitions might look something like this:\n\n```scdoc\n...\nenvs:\n - name: test\n serviceAccountPaths:\n synchronizer: \"your_keypath/synchronizer-manager-service-account.json\n udca: \"your_keypath/analytic-agent-service-account.json\n - name: prod\n serviceAccountPaths:\n synchronizer: \"your_keypath/synchronizer-manager-service-account.json\n udca: \"your_keypath/analytic-agent-service-account.json\n...\n```\n\nTo delete the **prod** environment, follow these steps:\n\n1. Get your gcloud authentication credentials: \n\n ```\n TOKEN=$(gcloud auth print-access-token)\n ```\n2. Delete the environment from any associated environment groups, one at a time:\n\n ### No data residency\n\n ```\n curl -X DELETE -H \"Authorization: Bearer $TOKEN\" \\\n \"https://apigee.googleapis.com/v1/organizations/$ORG_NAME/envgroups/$ENV_GROUP/attachments/prod\"\n ```\n\n ### Data residency\n\n ```\n curl -X DELETE -H \"Authorization: Bearer $TOKEN\" \\\n \"https://$CONTROL_PLANE_LOCATION-apigee.googleapis.com/v1/organizations/$ORG_NAME/envgroups/$ENV_GROUP/attachments/prod\"\n ```\n3. Do a dry run to test removal of the runtime components: \n\n ```\n helm delete $ENV_NAME -n apigee --dry-run\n ```\n\n The `--dry-run` command will return the same results as the command without the\n `--dry-run` option. For example: \n\n helm -n apigee delete example-env\n release \"example-env\" uninstalled\n\n4. If the dry run is error-free, remove the runtime components: \n\n ```\n helm delete $ENV_NAME -n apigee\n ```\n5. Open your overrides file and remove the `prod` environment definition from `envs` and `virtualhosts`, leaving only the **test** definitions. For example: \n\n ```scdoc\n ...\n envs:\n - name: test\n serviceAccountPaths:\n synchronizer: \"your_keypath/synchronizer-manager-service-account.json\n udca: \"your_keypath/analytic-agent-service-account.json\n ...\n ```\n6. Save the file."]]
