The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.94 release.
Requirements
MongoDB 7 or above is required. Elastic Search 6.8.6 or above is required.
Support for ARM-64
Each image manifest ships with two images for amd64 (Intel) and arm64 (aarch64).
This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being 10% cheaper than x86-64.
In addition, infrastructures such AWS have made it easy and cost-effective to deploy ARM aarch64 architectures using instance types that support the AWS Graviton family of processors.
Redis
If you're running the UI containers in a cluster, you will need to upgrade your version of Redis to 6.x or above. We ship sample kits that provide configurations using Redis 6.2.7.
You are free to use newer versions of Redis including 7.x and beyond.
Upgrade
We offer an upgrade tool that you must use to ensure that your installation is properly configured and optimized.
This upgrade tool is provided as part of the Cloud CMS Command Line Client. You can learn more about the client here: https://gitana.io/documentation/gitana/3.2/guide/guide/cli.html
You will need to install the Cloud CMS Command Line Client and configure it to connect to your Cloud CMS installation. Make sure that your Cloud CMS installation is up and running (on the new version of Cloud CMS) before using the tool.
You can then run the following:
cloudcms upgrade check --username <username> --password <password>
Where username and password are the credentials for your admin user.
This will check your installation to determine whether any upgrade steps are required.
If the check determines that upgrade steps are required, you can run them like this:
cloudcms upgrade apply --username <username> --password <password>
API Cluster Restart
You will need to perform a cold restart of your API cluster after upgrade.
Updates
API Server
New Features
- Added an admin API route to explicitly invalidate the principals cache (
/maint/cache/principals). - Added a compatibility filter to make some URLs backwards compatible and solve for cases where legacy URLs may be malformed.
Enhancements
- Applied updates to address latest CVE security scan.
- The CLI branch repair function now supports a commit option to automatically repair dangling associations in a branch.
- The dictionary view cache size has been increased to 500.
- Updated various third-party dependencies to the latest version.
- Improvement to how various subsystems including ping report verison info.
- When finalizing a release, the background worker is now limited explicitly to 1 running job per release ID. This prevent multiple finalizer calls from running at the same time across the cluster.
- Refresh and access tokens are now automatically cleaned up whenever a case arises where duplicate tokens were somehow stored in a collection.
- Enhanced the error message provided when a node is not found during a traversal.
Fixes
- Fix so that presigned URL generation for S3 and CloudFront now correctly fallback to the service descriptor credentials ahead of OS-provided crednetials.
- Fix so that persisted collections within Hazelcast will no longer encounter the "Cannot read 4 bytes!" error for cases where heap near-cache is used for cache optimization.
- Fix so that streams from S3 properly support
isAvailable()when using the asynchronous S3 client. - Fix so that tag modifications (create, update) cannot errantly remove a tag for certain edge cases.
- Fix so that graph operations against graphs with missing association targets (i.e. "dangling associations") will continue to work in some cases and provided better error messages in other cases.
UI Server
Enhancements
- Applied updates to address latest CVE security scan.
- Updated various third-party dependencies to the latest version.
- Improvement to how various subsystems including ping report verison info.
- Faster page, form and layout rendering + reduction of HTTP calls during navigation.
Webshot Server
Enhancements
- The core engine has been refactored to be faster and more efficient (now uses Puppeteer, Express 5, SSRF protection).
- The image has been hardened to reduce vulnerabilities.
Antivirus Server
Enhancements
- The core engine has been refactored to be faster and more efficient (Modernized dependencies and rewrite server with async/await).
- The image has been hardened to reduce vulnerabilities.
- Updated various third-party dependencies to the latest version.