[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[[["\u003cp\u003eThis documentation explains the process for deleting environments within Apigee hybrid, using the example of deleting a "prod" environment.\u003c/p\u003e\n"],["\u003cp\u003eDeleting an environment requires first removing it from any associated environment groups using a \u003ccode\u003eDELETE\u003c/code\u003e request with the \u003ccode\u003ecurl\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eBefore fully removing the runtime components, a dry run should be executed using either \u003ccode\u003ehelm delete --dry-run\u003c/code\u003e or \u003ccode\u003e$APIGEECTL_HOME/apigeectl delete --dry-run=client\u003c/code\u003e to check for errors.\u003c/p\u003e\n"],["\u003cp\u003eAfter a successful dry run, the runtime components can be permanently removed using \u003ccode\u003ehelm delete ENV_NAME\u003c/code\u003e or \u003ccode\u003e$APIGEECTL_HOME/apigeectl delete\u003c/code\u003e, depending on your setup.\u003c/p\u003e\n"],["\u003cp\u003eThe final step involves manually removing the environment's definition from the overrides file, specifically from the \u003ccode\u003eenvs\u003c/code\u003e and \u003ccode\u003evirtualhosts\u003c/code\u003e sections.\u003c/p\u003e\n"]]],[],null,[]]