Cloud CMS Release 3.2.65
Published on 03/15/2021
Update Recommendations (On-Premise Only)
With this version of Cloud CMS, we have disabled the deprecated Elastic Search Transport Client and have switched to using our Condor HTTP client. As such, connectivity between the api
and elasticsearch
services are no longer using port 9300
by default. They are now using port 9200
by default.
Please check your configuration to make sure that the API can connect to Elastic Search’s HTTP Endpoint.
For information on configuring Elastic Search for Cloud CMS, please see:
https://gitana.io/documentation/docker/configuration/api-server.html#using-the-condor-http-client
For improved performance, we recommend you rebuild your cluster indexes. To do so, we recommend using the reindex-datastore
command via the Cloud CMS Command Line Client (https://gitana.io/documentation/cli.html#reindex-datastore).
You can execute it like this:
cloudcms admin reindex-datastore --datastoreTypeId cluster --datastoreId default --children --username <username> --password <password>
Where the username
and password
are the credentials for your administrator account.
Enhancements
Branches / Snapshots
- Added an API method to support creation of snapshots asynchronously (using job polling). This is now used by the Cloud CMS command line client.
Logging
- Improved usage of asynchronous loggers across the board, resulting in a lower memory footprint and lower IO lock contention across threads. If you have custom
log4j2*.xml
files in place (for custom rolling file appenders or auditing log capture), you will need to adjust those configuration files slightly as described here: https://gitana.io/documentation/docker/configuration/api-server.html#default-configuration.
Transfer
- Faster transfer exports that are more efficient and use less memory. This is notable for copy, move, publish and deploy operations for a large number of nodes or objects.
Search
- Inspection of search indexes with REST API now includes ES mappings information.
User Interface
- Simplified the Project Export wizard so that it performs compressed exports of the master branch. To export multiple branches or run without compression, please use the command line, API or drivers.
Bug Fixes
AWS CloudWatch
- Fix so that the AWS CloudWatch Appender handles cases where log event messages are filtered out ahead of being invoked (which could result in empty messages).
Branches
- Fix so that MongoDB branch-level collections are always cleaned up properly for cases where a failure occurs during branch creation.
GraphQL
- Fix so that GraphQL queries are entirely isolated from node caches so as to prevent issues when querying nodes.
Merge
- Fix so that merges of branches works as intended when operating within older, legacy repositories.
Node
- Fix so that nodes read properly by considering case insensitivty when using a projections to tokenize the path.
Search
- Fix to search type filtering so that the
__type
property can be search as intended.
Transfer
- Fix so that imported Node attachments are automatically indexed into Elastic Search upon for all cases.
User Interface
- Fix so that unlocking the attempted login lock is picked up immediately by the user interface. This allows unlocked users to retry their login right away.
- Fix so that the Delete Project User action checks permissions against the project, allowing Project Managers to remove users from a project.
- Fix so that Attachment Pickers validate extensions (if so configured) for existing attachments.
- Fix so that the “required” property is handled properly for some nested cases.
Ready to Get Started?
Unlock your data with smart content services and real-time deployment