During a basic installation, you likely set up a single environment for testing. Most Apigee hybrid installations, however, have multiple environments. For example, a common use case is to have a test environment and a production environment.
If you have multiple environments, each one must have its own unique DNS name; for example, the test and prod environments might have the foo-test.mydomain.com and foo-prod.mydomain.com DNS names.
DNS names map to host aliases in a hybrid configuration. If you are familiar with virtual hosts in Apigee Edge, the concept of a host alias in hybrid is similar.
In addition to defining the orgName and envName properties, you must also specify a host alias and its TLS properties for each environment definition in the envs array.
For testing purposes only, you can use a self-signed certificate, as described in Create a self-signed certificate/key pair.
The DNS name for your server. For example, foo-test.mydomain.com. If you don't have a DNS name, you can use a wildcard (*).
If you have multiple environments, you must use a unique host alias name for each one. For example, foo-test.mydomain.com and foo-prod.mydomain.com.
NOTE: You cannot use a wildcard for the host name in a multiple environment configuration. If you do so, traffic will only be routed to one environment.
This property is required when configuring a host alias.
The path on your system to a TLS certificate file.
NOTE: The Common Name (CN) in the cert must match the value of hostAlias. When configuring multiple environments, each CN must match the hostAlias for its environment.
The path on your system to a TLS key file.