You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the version number of MAS and CLI are independently allocated. So It is hard to find the stable CLI version to install specific MAS version. If we assign the version number with the corresponding MAS that can be installed by the CLI, It is very use full to identify which CLI should be used.
Usage example
For example, if MAS version is v9.1.1, and core implementation of CLI version is 1.2.3, then CLI version can be v9.1.1.cli.1.2.3.
The text was updated successfully, but these errors were encountered:
The version of MAS has no direct bearing on the version of the CLI to use/there is not a 1:1 relationship.
We publish the recommended versions of the CLI to use for installing older catalogs so that customers can use versions of the CLI that were tested with the same catalog they want to use; generally speaking any version of the CLI will support the most recent 4 months worth of catalogs, so when installing older catalogs for whatever reason, older versions of the CLI should be used.
Feature and motivation
Currently the version number of MAS and CLI are independently allocated. So It is hard to find the stable CLI version to install specific MAS version. If we assign the version number with the corresponding MAS that can be installed by the CLI, It is very use full to identify which CLI should be used.
Usage example
For example, if MAS version is
v9.1.1
, and core implementation of CLI version is1.2.3
, then CLI version can bev9.1.1.cli.1.2.3
.The text was updated successfully, but these errors were encountered: