16.03.02 - Apigee Edge for Public Cloud release notes

On Thursday, March 3, 2016, we released a new version of Apigee Edge for Public Cloud.

New features and enhancements

Following are the new features and enhancements in this release.

API proxy chaining

Edge supports local API proxy chaining, which allows one API proxy to call another API proxy deployed in your Edge organization without additional network overhead. Previously, API proxy chaining required an http(s) call to another API proxy, which forwarded the request through a load balancer, router, and message processor.

New LocalTargetConnection elements are available on an API proxy's TargetEndpoint, allowing you to specify an API proxy name, the name of a specific ProxyEndpoint within an API proxy, or simply the Base Path to a local API proxy resource (such as /v1/myresource). The proxy editor UI also provides these options when you add or update a TargetEndpoint.

For more information, see Chaining API proxies together. The new LocalTargetConnection elements are also listed in the XML schema here: https://github.com/apigee/api-platform-samples/blob/master/schemas/configuration/configuration_schemas.xsd. (MGMT-3049)

Bugs fixed

The following bugs are fixed in this release.

Issue ID Description
MGMT-3083 Node.js Logs auto-refresh is too verbose with log messages
DEVRT-2275 Custom Attribute rate plans show only 5 attributes
DEVRT-1275 Not all developers are shown in the Rate Plan drop-down menu
DEVRT-1074 Prepaid Developer with zero balance throws NullpointerException when credit is applied