On August 27, 2020, we released Apigee hybrid runtime version 1.3.2.
Help & notifications
Apigee hybrid version 1.3.x to version 1.3.2
To upgrade from hybrid version 1.3.x to version 1.3.2, download the new
hybrid runtime, and run
apigeectl init and
|Platform||Download hybrid runtime|
|Mac 64 bit||
curl -LO \ https://storage.googleapis.com/apigee-public/apigee-hybrid-setup/1.3.2/apigeectl_mac_64.tar.gz
|Linux 64 bit||
curl -LO \ https://storage.googleapis.com/apigee-public/apigee-hybrid-setup/1.3.2/apigeectl_linux_64.tar.gz
|Mac 32 bit||
curl -LO \ https://storage.googleapis.com/apigee-public/apigee-hybrid-setup/1.3.2/apigeectl_mac_32.tar.gz
|Linux 32 bit||
curl -LO \ https://storage.googleapis.com/apigee-public/apigee-hybrid-setup/1.3.2/apigeectl_linux_32.tar.gz
Apigee hybrid version 1.2.0 to version 1.3.2
To upgrade from hybrid version 1.2.0 to version 1.3.2 follow the instructions in Upgrading Apigee hybrid to version 1.3.2.
Apigee hybrid version 1.1.1 or older to version 1.3.2
If you are upgrading from Apigee hybrid version 1.0 or 1.1, you must first upgrade to hybrid version 1.2 before upgrading to version 1.3.2. See the instructions for Upgrading Apigee hybrid to version 1.2.
For new features and changes introduced in Apigee hybrid version 1.3.1, see the 1.3.1 - Apigee hybrid runtime release notes
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.
|162759110||Base paths consisting of only "
|2668578||GKE On Prem - WATCHER would fail to connect to apigee.googleapis.com when HTTP_PROXY is configured.|
|143659917||The PopulateCache policy's expiration setting had to be set to an explicit value between 1 and 30.|
The following table describes the known issues for this release:
Double slashes (
|161658025||Inaccurate deployment status for Shared Flows
For Shared Flows, the deployment status is not being reported correctly to the UI, resulting in an indefinitely spinning deployment icon. If you have deployed a Shared Flow and see the spinning deployment icon, you must assume that the deployment has in fact failed.
To obtain the correct deployment status, use the v1.organizations.environments.sharedflows.revisions.deployments API. For example:
|146222881||Invalid HTTP Header error: The Istio ingress switches all incoming target responses to the
HTTP2 protocol. Because the hybrid message processor only supports HTTP1, you may see the
following error when an API proxy is called:
If you see this error, you can take either of the following actions to correct the problem: