Apigee Edge for Private Cloud 4.17.05 Is Here!
We’re excited to announce the general availability of Apigee Edge for Private Cloud 4.17.05. This release includes several features and bug fixes that help you better control and secure your APIs, standardize deployment, enable reusability of existing infrastructure components, and make it easy to manage developer apps.
API proxy URL rendering
In most cases, the URL displayed in the Edge UI is the correct URL for making external requests to the proxy. However, for some configurations, the displayed URL is not correct. Any one of the following configurations can cause the displayed URL to not correspond to the actual URL used to make external requests to the proxy:
- SSL termination occurs at a load balancer
- Port mapping occurs between a load balancer and Apigee routers
- Path rewriting is configured in a load balancer
Edge for Private Cloud 4.17.05 provides support for overriding the URL displayed by the Edge UI.
Zero-downtime shared flows deployment
To minimize the potential for downtime during deployment, you can now employ shared flows, which enable you to combine policies and resources that are consumable from multiple API proxies, with an override option.
In essence, by setting the override to “true,” the current revision of the shared flow is removed once the new revision’s deployment is complete.
Deleting monetization data for an organization
You can now delete monetization data for your organization. This is important if, for example, you create a monetization package or rate plan for testing purposes, and need to clear it when done.
Still using the Apigee secure store?
The Apigee secure store, or vault, which provides encrypted storage of key/value pairs, is created with the management API and accessed at runtime with functions in the apigee-access Node.js module.
We’ve deprecated the secure store. Now, you should use encrypted key value maps (KVMs), as described in Working with Key Value maps. Encrypted KVMs are as secure as vaults, but provide more options for creation and retrieval.
We’ve made a host of other improvements, including:
- Stricter input validation across all entities in an organization. The allowed characters are alphabets (upper and lower cases), numbers, and underscore.
- We’ve introduced the SMTPMAILFROM parameter in the Edge installation. This parameter specifies the “from/sender” email address used when Edge sends automated emails.
- We’ve written new documentation on changing default system user, enabling debug logging, and Edge install tasks roles (root and non-root).
- Support for setting API timeout duration used by Edge UI to control how long the UI waits for an API management call to return before issuing a timeout error message.
How to upgrade
We strongly encourage customers to upgrade to this new release to start benefitting from the newly added features, UI enhancements, and bug fixes as soon as possible. You can update Apigee Edge version 4.17.01.0x to 4.17.05. If you have a version of Edge previous to version 4.16.01, then you must first migrate to version 4.16.x and update to version 4.17.05.
Hope you’re as excited as we are about this new release. There’s a lot more to share than what can fit here; additional details can be found in our release notes.
If you have questions, comments, or feedback, start a conversation on Apigee Community.
Image: Flickr Creative Commons / debaird