4.52.00.02 - Edge for Private Cloud release notes

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

On July 25, 2023, we released a new version of Apigee Edge for Private Cloud.

Note: This version will be supported until August 31, 2024.

Update procedure

This section describes how to install this release if you are updating from the previous release of Edge for Private Cloud. If you need to update from an earlier release, see Applying multiple patch versions.

Updating this release will update the components in the following list of RPMs:

• edge-gateway-4.52.00-0.0.60193.noarch.rpm
• edge-management-server-4.52.00-0.0.60193.noarch.rpm
• edge-postgres-server-4.52.00-0.0.60193.noarch.rpm
• edge-qpid-server-4.52.00-0.0.60193.noarch.rpm
• edge-router-4.52.00-0.0.60193.noarch.rpm
• apigee-cassandra-client-2.1.22-0.0.2521.noarch.rpm
• edge-analytics-4.52.00-0.0.40092.noarch.rpm
• apigee-sosreport-5.0-0.0.2513.noarch.rpm
• edge-management-ui-static-4.52.00-0.0.20045.noarch.rpm
• apigee-configutil-4.52.00-0.0.621.noarch.rpm
• apigee-postgresql-14.5-0.0.2743.noarch.rpm

You can check the RPM versions you currently have installed, to see if they need to be updated, by entering:

apigee-all version

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.52.00 bootstrap_4.52.00.sh file to /tmp/bootstrap_4.52.00.sh:

      curl https://software.apigee.com/bootstrap_4.52.00.sh -o /tmp/bootstrap_4.52.00.sh

   3. Install the Edge 4.52.00 apigee-service utility and dependencies:

      sudo bash /tmp/bootstrap_4.52.00.sh apigeeuser=uName apigeepassword=pWord

      where uName and pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.

   4. Use the source command to execute the apigee-service.sh script:

      source /etc/profile.d/apigee-service.sh

2. Update Postgres nodes (master and standby):

   /opt/apigee/apigee-setup/bin/update.sh -c ps -f configFile

3. Update Analytics on the Management server node :

   apigee-service edge-analytics update

4. On all Edge nodes, execute the update.sh script for the edge process:

   /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile

5. If you are using the New Edge experience, execute the following commands:

   apigee-service edge-management-ui-static update

   /opt/apigee/apigee-setup/bin/update.sh -c ue -f configFile

Security issues fixed

No security issues were fixed in this release.

Changes to supported software

There are no changes to supported software in this release.

Deprecations and retirements

There.

There are no new deprecations or retirements in this release.

New features

This release introduces the following new feature:

Audit records automatically deleted 400 days after creation

A feature was added to automatically delete audit records 400 days after creation. Previously, audit records were created without a time to live, so they accumulated in Cassandra.

You can revert this feature to never delete audit records by setting conf_audit_cassandra.ttl.value to -1 on management server. You can also change the number of days you want to retain audit records by modifying the value of conf_audit_cassandra.ttl.value in milliseconds on management server. Note that this feature only applies to newly generated audit records, but not to audit records generated in your system in the past.

Enhancement to conf_keymanagement_oauth_refresh_token_expiry_time_in_millis

The conf_keymanagement_oauth_refresh_token_expiry_time_in_millis configuration override now not only sets the default token expiry time but also provides a ceiling for the refresh token expiry in Cassandra.

Bug fixes

This section lists the Private Cloud bugs that were fixed in this release.

Issue ID	Description
234582218	The token calculator Python script apigee-cassandra-calc.py, which is used to calculate start tokens for a Cassandra ring based on the CASS_HOSTS property in the silent config file, was not working correctly. This has been fixed.
274884575	Certain stats API calls with a dimension containing groupid were failing. This has been fixed.
286971552	Fixed Postgres scripts in edge-postgres-server in the silent config file, so that they work with default values of variables that are not specified, during installation
276444350	After upgrading Edge for Private Cloud to the latest version, it was not possible to add, view, or edit the virtual host details in the new Edge UI at Admin > Virtual Hosts. This has been fixed.
277723022	A fix was made to config.log to preserve historical changes in the log.

Known issues

See Known issues with Edge for Private Cloud for a complete list of known issues.

Applying multiple patch versions

This section describes how to apply multiple patch versions, in case you are updating from a version of Edge for Private Cloud that is earlier than the previous patch release version.

Each patch release contains updates to specific components of Edge for Private Cloud, such as edge-management-server. To apply multiple patch versions, you need to update each Edge component that was included in a patch release later than your currently installed version. You can find these components by looking at the Edge for Private Cloud release notes for all versions later than your current version, and checking the list of RPMs for those releases. See Apigee Release Notes for links to all Edge for Private Cloud release notes.

Note: You only need to update each component once, by installing the RPM for the latest version of the component included in the patch releases. Follow the instructions in the release notes for that version to update the component.

Note: Upgrading a component automatically installs the latest patch version of a component. If you want to upgrade to a patch version that is not the latest, you need to maintain your own tarball copy of Apigee's repo using Apigee mirror, and use this mirror for Apigee installations. For more information, refer to Using a local Edge repository to maintain your Edge version.