180302 - Apigee Edge for Public Cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info

On Tuesday, March 20, 2018, we began releasing a new version of Apigee Edge for Public Cloud.

Private Cloud customers: Is this cloud release included in your Private Cloud version? See your version's release notes to see which cloud releases it contains. Also, see About release numbering to understand how you can figure it out by comparing release numbers.

Questions or issues? Get help here .

Release notifications: Go to http://status.apigee.com and click Subscribe to Updates.

Release notes home page

Deprecations and Retirements

The following features are being deprecated or retired. See the Apigee deprecation policy for more information.

Issue ID	Component Name	Description
74622499	API Runtime	Remove property conf_http_HTTPClient.disable.url.hostname.validation This property to disable hostname validations is redundant and will be removed in the next cloud release.

Issue ID

Component Name

Description

74622499

API Runtime

Remove property conf_http_HTTPClient.disable.url.hostname.validation

This property to disable hostname validations is redundant and will be removed in the next cloud release.

New Features and Updates

Following are the new features and updates in this release.

Issue ID	Component Name	Description
71861442	Management Server	Proxy bundle import/update optimizations Edge will perform stronger validation on API proxy bundles at deploy time. This update helps ensure faster deployments while reducing deployment failures and bundle corruptions when more than one user imports the same bundle at the same time. Following are notable changes and behaviors: Each bundle must have a file system root of `/apiproxy`. Edge no longer attempts to ignore paths in an API proxy bundle's resources folder. (For example, Edge no longer ignores .git or .svn directories.) If a bundle contains an invalid configuration of more than one API proxy XML configuration file (for example, apiproxy/proxy1.xml and apiproxy/proxy2.xml), there is no guarantee which configuration is used for the API proxy.
68943054	API Runtime	Make health checks use Apigee DNS cache
65738755	Turbo (Hosted Targets)	Improved error message from MGMT for HT deploy API fail
64845308	Turbo (Hosted Targets)	Disable Trireme for new orgs after Beta

Bugs Fixed

The following bugs are fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.

Issue ID	Component Name	Description
74056492	API Runtime	DNS refresh does not happen after all IPs are removed from list unless actual DNS entry changes
74000624	Turbo (Hosted Targets)	Modify default config value for Node.js Trireme restart logic
73496048	API Runtime	TTL from cache resource definition is not respected for CPS orgs when expiry settings has tag with empty values
73347561	Management Server	registration.ServerDoesNotExist Error scenario deploying API Proxies
73254073	Management Server	Org admin permissions should not list vhost related resources if it's not restricted
73164241	Management Server	SecureStoreNotFound and StoreItemNotFound should be thrown as 404 instead of 5XX Caution: The following HTTP status code changes apply to the management API for vaults (secure stores) at the organization and environment scopes. If you're checking for different response codes in scripts or monitoring, be sure to update your code accordingly. Now 404 status code instead of 500 On GET, POST, PUT, and DELETE operations on a vault that doesn't exist, a 404 response is returned with the error `securestore.DoesNotExist`. On GET, POST, PUT, and DELETE operations on an item in a vault that doesn't exist, a 404 response is returned with the error `securestore.StoreItemDoesNotExist`. 409 status code When trying to create an item in a vault, and the item already exists, a 409 response is returned with the error `securestore.StoreItemAlreadyExists`.
73016051	API Runtime	proxy import fails if proxy.xml file has double slash
72990985	Management Server	Incorrect list of developers returned from the management API
72951198	Turbo (Hosted Targets)	HTTP Timeouts from the MP -> Turbo (Hosted Targets) during deployment
72806072	API Runtime	Quota policy start time is not honored for \"calendar\" in Core Persistence Services (CPS) In the Quota policy, when you configure a `calendar` quota type, the `StartTime` element lets you define a specific date and time for quota to begin counting API calls. The start time also affects the `Interval` and `TimeUnit` settings that determine the frequency with which the quota resets. In CPS-enabled organizations, the `StartTime` was being ignored, and quota was starting/resetting at the top of the hour rather than at the specified time. With this release, the Quota policy considers `StartTime` in CPS-enabled organizations.
71680710	Turbo (Hosted Targets)	Edge should create a new build when source hash matches but previous build failed.
69284606	API Runtime	\"Content-Encoding\" header dropped in request flow
68203882	API Runtime	Proxy un-deploy intermittent issue
67785822	API Runtime	Mask configuration not hiding sensitive data in trace