You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
New features and enhancements
Specify target connection protocol from the command line
The bind-route-service command now supports a protocol argument for
specifying whether your API proxy's endpoint is reached via HTTP or HTTPS. Previously, you had to
manually change the protocol after generating the proxy.
cf bind-route-service <your-app-domain> <service-instance> [--hostname <hostname>] \
-c '{"org":"<your edge org>","env":"<your edge env>",
"bearer":"'<authentication-token-file>'" | "basic":"<encoded-username-password>" | "<username>:<password>",
"action":"proxy"|"bind"|"proxy bind",
["protocol":"http"|"https"]}'
Bugs fixed
Unable to deploy to multiple availability zone environment
This release fixes an issue in deploying the Apigee Edge tile to a multiple availability zone environment by requiring metadata version 1.8.
Additional documentation
See the following links for documentation content:
- Edge integration with Pivotal Cloud Foundry (overview)
- Creating an Edge API proxy to manage client calls to your Cloud Foundry application (using the service broker with Pivotal Cloud Foundry)
- Apigee Edge Microgateway Add-ons for Cloud Foundry (running Edge Microgateway in Cloud Foundry)
- Cloud Foundry Service Broker for Apigee (installing the service broker from source)