Add a new environment definition to the envs[] property in your overrides file.
Note that the property is an array; therefore, you can add more than one environment definition
to it.
Give the new environment the same name as the one you created in the UI.
For example, the following configuration defines two environments: test
and prod:
[[["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-25 UTC."],[[["\u003cp\u003eThis documentation pertains to Apigee hybrid version 1.4, which is now end-of-life and requires an upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eCreating a new environment in Apigee hybrid involves first creating the environment in the management plane via the UI or API, and then adding its configuration to your overrides file.\u003c/p\u003e\n"],["\u003cp\u003eMultiple environments can be defined simultaneously within the \u003ccode\u003eenvs[]\u003c/code\u003e property of the overrides file, with each environment's name matching the one created in the UI.\u003c/p\u003e\n"],["\u003cp\u003eChanges to environment configurations in the overrides file need to be applied to the cluster using the \u003ccode\u003eapigeectl apply\u003c/code\u003e command with the \u003ccode\u003e--all-envs\u003c/code\u003e flag.\u003c/p\u003e\n"]]],[],null,[]]