Cloud CMS Release 3.2.61a

The following are the new features, enhancements and fixed issues for Cloud CMS 3.2.61a release.

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.

New Features

The following features have been backported from 3.2.62 to 3.2.61a:

Command Line Interface

• The CLI now supports transfer commands to enable developers or administrators to script the import and export of projects, repositories, branches, nodes and more.
• Now supports Node 15.x and beyond.

Supported Stacks

• Added support for MongoDB 4.0.21
• Added support for Elastic Search 6.8 and 7.9
• Added support for AWS ElasticSearch 6.8 and 7.9