You're viewing Apigee Edge documentation.
View Apigee X documentation.
On the following dates, we began releasing component updates to Apigee Edge for Public Cloud:
- Router: Wednesday, September 2, 2020
Help & notifications
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.
New features and updates
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|
Router fails to get new keystore
The router has the capability of retrying failed updates for virtual hosts and key stores. If SSL keys are not available, the virtual hosts will fail to load. In this event, an internal retry is fired on the routers with exponential delay. If the failures are caused by Cassandra replication, the routers will eventually catch up when the keys are replicated. In this situation, manually restarting the router is not necessary.
TLS certificates not updated in Apigee Routers
Possible errors are now being handled by the router, and errors are communicated back to the management server with the details.
Router causing cascading failures to vhosts and creating .bad files
Make sure a rollback is clean when the keys are not successfully applied. Return errors during configuration to the management server.