Go to Environments

• Name: The programmatic environment name. TheName can't be changed after it is created.

  The name must contain between 2 and 32 characters which can be lower-case letters, numbers, or hyphens. The name must begin with a letter and cannot end with a hyphen. The name must be different from any other environment name in your organization.

• Display Name: The name for the environment that is displayed in the UI.
• Description: Optional. A description of the environment.
• Instance: Leave theInstance field blank. Instances do not apply to Apigee hybrid installations.
• Environment group: Leave theEnvironment group field blank for now. You will create an environment group in the next procedure.
• Deployment type: For most Apigee hybrid installations, select the option to deploy individual API proxies. You can optionally deploy an archive of your API proxy configuration environment. For more information, seeSupported deployment types.Note: The deployment type used with this environment cannot be changed after the environment is created.

On the command line, get yourgcloud authentication credentials using the following command:

export TOKEN=$(gcloud auth print-access-token)

echo $TOKEN

for /f "tokens=*" %a in ('gcloud auth print-access-token') do set TOKEN=%a

echo %TOKEN%

export ENV_NAME="YOUR_ENV_NAME"

set ENV_NAME="YOUR_ENV_NAME"

Where:

• ENV_NAME(Required) The environment name can contain lowercase letters, dashes, and numbers and must start with a lowercase letter. This name will be used as the identifier and cannot be changed after creation of the environment.

curl -H "Authorization: Bearer$TOKEN" -X POST -H "content-type:application/json"   -d '{    "name": "'"$ENV_NAME"'"  }'   "https://apigee.googleapis.com/v1/organizations/$ORG_NAME/environments"

curl -H "Authorization: Bearer$TOKEN" -X POST -H "content-type:application/json"   -d '{    "name": "'"$ENV_NAME"'"  }'   "https://$CONTROL_PLANE_LOCATION-apigee.googleapis.com/v1/organizations/$ORG_NAME/environments"

On a successful creation request, the Environments API should respond with a message similar to the following:

{"name":"organizations/hybrid-example/operations/c2aee040-7e79-4fd4-b0cf-79ca1b7098a8","metadata":{"@type":"type.googleapis.com/google.cloud.apigee.v1.OperationMetadata","operationType":"INSERT","targetResourceName":"organizations/hybrid-example/environments/example-env","state":"IN_PROGRESS"}}

As thestate property in the response indicates, Apigee has started to create the new environment, so its state isIN_PROGRESS.

curl -H "Authorization: Bearer$TOKEN" \          "https://apigee.googleapis.com/v1/organizations/$ORG_NAME/environments"

curl -H "Authorization: Bearer$TOKEN" \          "https://$CONTROL_PLANE_LOCATION-apigee.googleapis.com/v1/organizations/$ORG_NAME/environments"

On a successful creation request, the Environments API responds with a message similar to the following:

[  "your-environment-name"]

Go to Environment Groups

• Environment group name: A name for the environment group. The name must start and end with an alphanumeric character. It can have up to 63 characters consisting of alphanumeric characters and hyphens. The name must be different from any existing environment group name in your organization.

• Hostames: A list of host names that can be used to call proxies. Each host name must be on a separate line.

  Note: The names assigned to an environment group must be unique to that group: they can't be used by other environment groups.

  You also have the option to clickConfigure Google Load Balancer with these domains. This opens theLoad balancing page in the Cloud console, where you can configure load balancing for the host names.

• Environments: An optional list of environments to include in the environment group.

On the command line, get yourgcloud authentication credentials using the following command:

TOKEN=$(gcloud auth print-access-token)

for /f "tokens=*" %a in ('gcloud auth print-access-token') do set TOKEN=%a