You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Monday, March 6, 2017, we began releasing a new version of Apigee Edge for Public Cloud.
Deprecations and retirements
The following features are being deprecated or retired. See the Edge deprecation policy for more information. See Apigee deprecations and retirements for the dates around which features will be retired (removed from the product).
Deprecation of classic persistence framework
Like many of our customers, Apigee has embraced a microservices-based architecture, and this has improved the reliability and scalability of our products, as well as the way we develop and deliver them. As part of that effort, we're rolling out our next generation Core Persistence Services (CPS) in a limited fashion, and new customers will begin to use these new management APIs. Eventually, all customers will be on CPS. For more information, see About Core Persistence Services (CPS) and CPS retirements and changes. (CORESERV-836)
New features and updates
Following are the new features and updates in this release.
With this release, Edge will begin performing stricter naming and configuration validations on entities at deployment time. When entities you're trying to deploy are invalid, deployment will continue to succeed with a 200 HTTP status code, but you'll receive an Apigee Advisory error message that links you to more information. This gives you the opportunity to fix issues before validation is fully enforced in a future release, at which time deployments containing invalid entities will not succeed and result in an HTTP 400 status code error.
To find out about the validations being performed, see the Advisory messages reference. (MGMT-3576)
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.
|TPS analytics metric returns minutes, not seconds