[[["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 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,[]]