- Edge for Private Cloud release notes

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

On January 22, 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.19.01 bootstrap_4.19.01.sh file to /tmp/bootstrap_4.19.01.sh:
      curl https://software.apigee.com/bootstrap_4.19.01.sh -o /tmp/bootstrap_4.19.01.sh
    3. Install the Edge 4.19.01 apigee-service utility 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.

    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. Update all Message Processor, Router, and Management Server nodes. On each node, execute the following command:
    /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile

    Where configFile specifies the configuration file that you used to install Edge.

Deprecations and retirements


Bugs fixed

The following table lists the bugs fixed in this release:

Issue ID Description

Increased latency

There was an increase in target latency after a recent update which negatively affected API performance.


Security vulnerabilities in Message Processors

Updated Message Processors to address security vulnerabilities.


Shared flows not executing

Bundles with shared flows that were deployed from a different region were not executing on some MPs.


TLS failures with trial.mode set to true

TLS certificates were failing when the Router configuration included the conf_router_is.free.trial.mode=true setting.


API calls to updated deployments with SharedFlow

After updating a deployment with a SharedFlow, API calls to the following path were failing:


PHP package errors caused installation failures

Attempts to install portal with version 4.19.01 were failing with PHP package errors.


Slow Deployment API response time with override and delay

Calls to the Deployment API with override=true and a value set for delay were taking too long to return.