On August 10, 2020, we released a new version of Apigee Edge for Private Cloud.
To update your installation, perform the following procedure on the Edge nodes:
On all Edge nodes:
- Clean the Yum repos:
sudo yum clean all
- Download the latest Edge 4.19.01
curl https://software.apigee.com/bootstrap_4.19.01.sh -o /tmp/bootstrap_4.19.01.sh
- Install the Edge 4.19.01
apigee-serviceutility and dependencies:
sudo bash /tmp/bootstrap_4.19.01.sh apigeeuser=uName apigeepassword=pWord
Where uName:pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.
- Update the
sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
- Use the
sourcecommand to execute the
- Clean the Yum repos:
- On all Qpid nodes, update the
apigee-qpiddprocess by executing the following command:
/opt/apigee/apigee-setup/bin/update.sh -c qpid -f configFile
where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud. For example,
- On all Edge nodes, execute the
update.shscript for the
edgeprocess. To do this, execute the following command on each node:
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
- On all portal nodes, update the
devportalprocess by executing the following command:
/opt/apigee/apigee-setup/bin/update.sh -c dp -f configFile
Deprecations and retirements
privateKeyExportable query parameter on the
Aliases API has
The following table lists the bugs fixed in this release:
Revenue reports (Monetization)
Revenue reports were showing incorrect data for some fields, including net price and revenue shares. The reports are now showing the correct data.
Some customers were experiencing a
Qpid depedency conflicts
In some cases, Linux systems were experiencing package dependency conflicts when upgrading Qpid services that were also used by Edge.
'Try the new UI' link removed
The 'Try the new UI' link under the title when logging in to the Classic Edge UI has been removed.
When undeploying an API proxy that had multiple shared flow revisions in the same environment, Edge did not undeploy the revision and returned the following error:
The Shared flow preProxyFlow is in use by PreProxyFlowHook
Drupal security updates
The following security updates have been added to Edge:
The RPMs apigee-drupal-7.72 all have different build numbers:
These RPMs all have the same version of Drupal core 7.72 and are identical. If you upgrade from earlier versions, the build number on the RPM may not change.