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:
Öffnen Sie die Überschreibungendatei und entfernen Sie die Umgebungsdefinition test aus envs und virtualhosts. Behalten Sie nur die prod-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 explains how to delete environments within Apigee hybrid, which involves removing both runtime components and management plane configurations.\u003c/p\u003e\n"],["\u003cp\u003eThe process requires first obtaining gcloud authentication credentials and then deleting the target environment from any associated environment groups.\u003c/p\u003e\n"],["\u003cp\u003eA dry run is recommended to test the removal of runtime components before executing the actual removal.\u003c/p\u003e\n"],["\u003cp\u003eAfter deleting the environment from the management plane, you must manually update the overrides file to remove the environment's definitions from the \u003ccode\u003eenvs\u003c/code\u003e and \u003ccode\u003evirtualhosts\u003c/code\u003e sections.\u003c/p\u003e\n"],["\u003cp\u003eThis documentation pertains to an end-of-life version (1.6) of Apigee hybrid, and users are advised to upgrade to a newer, supported version.\u003c/p\u003e\n"]]],[],null,["# Delete environments\n\n| You are currently viewing version 1.6 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 ```\n curl -X DELETE -H \"Authorization: Bearer $TOKEN\" \\\n \"https://apigee.googleapis.com/v1/organizations/$ORG_NAME/envgroups/$ENV_GROUP/attachments/$ATTACHMENT_ID\"\n ```\n Where \u003cvar translate=\"no\"\u003e$ATTACHMENT_ID\u003c/var\u003e is the system generated UUID.\n3. Do a dry run to test removal of the runtime components: \n\n ```\n apigeectl delete -f overrides.yaml --env=prod --dry-run=true\n ```\n4. If the dry run is error-free, remove the runtime components: \n\n ```\n apigeectl delete -f overrides.yaml --env=prod\n ```\n5. Delete the environment from the management plane: \n\n ```\n curl -X DELETE -H \"Authorization: Bearer $TOKEN\" \\\n \"https://apigee.googleapis.com/v1/organizations/$ORG_NAME/environments/prod\"\n ```\n6. Open your overrides file and remove the `test` environment definition from `envs` and `virtualhosts`, leaving only the **prod** definitions. For example: \n\n ```scdoc\n ...\n envs:\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 ```\n7. Save the file."]]
