- Edge for Private Cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation.

On August 6, 2020, we released a new version of Apigee Edge for Private Cloud.

Update procedure

To update your installation, perform the following procedure on the Edge nodes:

  1. On all Edge nodes:

    1. Clean the Yum repos:
      sudo yum clean all
    2. Download the latest Edge 4.50.00 bootstrap_4.50.00.sh file to /tmp/bootstrap_4.50.00.sh:
      curl https://software.apigee.com/bootstrap_4.50.00.sh -o /tmp/bootstrap_4.50.00.sh
    3. Install the Edge 4.50.00 apigee-service utility 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.

    4. Update the apigee-setup utility:
      sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
    5. Use the source command to execute the apigee-service.sh script:
      source /etc/profile.d/apigee-service.sh
  2. On all Edge nodes, execute the update.sh script for the edge process. 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, /opt/silent.conf.

  3. On all portal nodes, update the devportal process by executing the following command:
    /opt/apigee/apigee-setup/bin/update.sh -c dp -f configFile

Supported software

No changes.

Deprecations and retirements

The privateKeyExportable query parameter on the Aliases API has been deprecated.

New Features

No changes.

Bugs fixed

The following table lists the bugs fixed in this release:

Issue ID Description

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.


NoClassDefFoundError after patch installation

Some customers were experiencing a NoClassDefFoundError on the Management Server after installing patch


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, you can no longer deploy multiple shared flow revisions in the same environment, irrespective of whether the override parameter is set to true or false. This holds whether you are using the shared-flow deployment API with MIME content type application/octet-stream or type application/x-www-form-urlencoded. For more information, see the two examples in step 3 of this section of the shared flow documentation. If the shared flow is used in a flow hook, deploying a new revision of the shared flow will cause the flow hook to use the latest deployed revision.

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:

  • Drupal core: 7.72
  • Internationalization: 7.x-1.27
  • Services: 7.x-3.27

The RPMs apigee-drupal-7.72 all have different build numbers:

  • 4.19.01: apigee-drupal-7.72-0.0.304
  • 4.19.06: apigee-drupal-7.72-0.0.111
  • 4.50.00: apigee-drupal-7.72-0.0.113

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.