Create environments Stay organized with collections Save and categorize content based on your preferences.
This topic explains how to create new environments for Apigee hybrid. For an introduction, seeAbout environments and environment groups.
About environment creation
Environment creation is a two-step process:
- Create an environment in the management plane using either the UI or an Apigee API.
- Add configuration for that environment to your overrides file and apply it to the cluster.
The steps for adding an environment are described in adding and configuring an environment are explained inStep 5: Add an environment and Specify configuration overrides.
How to create an environment
- Create one or more new environments in theApigee UI or with theCreate environments API. For the basic steps, seeStep 5: Add an environment.
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 andprod:namespace:my-namespaceorg:my-organization...envs:-name:testserviceAccountPaths:synchronizer:"your_keypath/synchronizer-manager-service-account.json udca: "your_keypath/analytic-agent-service-account.json-name:prodserviceAccountPaths:synchronizer:"your_keypath/synchronizer-manager-service-account.json udca: "your_keypath/analytic-agent-service-account.json...
- Apply any changes to the cluster:
apigeectl apply -foverrides-file.yaml --all-envs
For more information about virtual host configuration seeConfigure virtual hosts. For a complete list of environment configuration elements, seeenvs in theConfiguration property reference.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-18 UTC.