You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On August 6, 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.50.00
curl https://software.apigee.com/bootstrap_4.50.00.sh -o /tmp/bootstrap_4.50.00.sh
- Install the Edge 4.50.00
apigee-serviceutility and dependencies:
sudo bash /tmp/bootstrap_4.50.00.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 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
where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud. For example,
- 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:
408 timeout errors
API requests for Virtual Host names were incorrectly returning 408 timeout errors.
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
Multiple shared flow revisions deployed in the same environment
When deploying a new revision of a shared flow, the prior revision and the new revision were being deployed to the same environment at the same time. Edge did not undeploy the prior revision, and the deployment status showed two revisions deployed at the same time.
As of version 4.50.00.01, you can no longer deploy multiple shared flow revisions
in the same environment,
irrespective of whether the
With this fix, only the new revision is allowed to be deployed, and prior revisions will be correctly undeployed.
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.