@celonis/content-cli 1.0.0 → 1.0.4

package/README.md

@@ -1,7 +1,7 @@
 # Content CLI
 
-Content CLI is a tool to help manage content in Celonis EMS. It provides various commands to help extract 
-content like analyses, packages, assets and others from your Celonis EMS team to your local machine, which 
+Content CLI is a tool to help manage content in Celonis Platform. It provides various commands to help extract 
+content like analyses, packages, assets and others from your Celonis Platform team to your local machine, which 
 you can then push to other teams. This process can be easily achieved by creating profiles for your different 
 teams and execute commands in a profile's context.
 
@@ -39,7 +39,7 @@ as part of our pycelonis examples library [here](https://github.com/celonis/pyce
 
 Content CLI has three core functionalities:
 
-**Profile:** The CLI connects to the EMS environments through profiles. For each of the commands you can specify 
+**Profile:** The CLI connects to the Celonis Platform environments through profiles. For each of the commands you can specify 
 which profile you want to use. This makes it powerful in the sense that you can pull something from let's say 
 team1.cluser1 and push it directly to team2.cluster2 easily. You can create a profile using the following command:
 
@@ -47,8 +47,8 @@ team1.cluser1 and push it directly to team2.cluster2 easily. You can create a pr
 content-cli profile create
 ```
 
-**Pull:** This feature allows you to download content from the EMS to your local machine. Let's take Studio package 
-as an example. These can be exported in the EMS as ZIP files that contain all package assets. By using the following 
+**Pull:** This feature allows you to download content from the Celonis Platform to your local machine. Let's take Studio package 
+as an example. These can be exported in the Celonis Platform as ZIP files that contain all package assets. By using the following 
 command using the package key and profile you have created, you will pull the ZIP file.
 
 ```
@@ -59,7 +59,7 @@ Example, if you want to pull a package with key "interesting-package" from your
 content-cli pull package -p my-dev-profile --key interesting-package
 ```
 
-**Push:** This feature allows you to push a content file to a team in the EMS. To continue the last example, 
+**Push:** This feature allows you to push a content file to a team in the Celonis Platform. To continue the last example, 
 you can use the following command to push he previously pulled package in another team.
 
 ```
@@ -84,7 +84,7 @@ content-cli pull package -h
 
 ## Building and Using the Project locally 
 
-This tool is tightly connected with the Celonis EMS and all capabilities require to have access to a Celonis EMS Team. 
+This tool is tightly connected with the Celonis Platform and all capabilities require to have access to a Celonis Platform Team. 
 After cloning the project, the next step is to install the project dependencies. We use `yarn` as our package manager, 
 so running `yarn install` on the project root folder should install all the necessary dependencies. After installing 
 the project dependencies, you can run `yarn build` to build the project artifact. To use the built artifact, you can 
@@ -92,6 +92,7 @@ run `node content-cli.js` in the generated `dist` folder.
 
 If we want to use a specific local build of the tool globally, we can do this by:
 - Move to the root directory of the project.
+- Execute `cd dist`, to move to the `dist` directory.
 - Execute the `npm link` command. 
 This will create a symbolic link in the global `node_modules` directory, allowing you to run the CLI from anywhere on your machine.
 

package/commands/studio/service/package.service.js

@@ -57,13 +57,13 @@ var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, ge
         }
         findAndExportListOfAllPackages(includeDependencies, packageKeys) {
             return __awaiter(this, void 0, void 0, function* () {
-                const fieldsToInclude = ["key", "name", "changeDate", "activatedDraftId", "workingDraftId", "spaceId"];
+                const fieldsToInclude = ["key", "name", "changeDate", "activatedDraftId", "workingDraftId", "spaceId", "id"];
                 let nodesListToExport = yield this.packageApi.findAllPackages();
                 if (packageKeys.length > 0) {
                     nodesListToExport = nodesListToExport.filter(node => packageKeys.includes(node.rootNodeKey));
                 }
                 if (includeDependencies) {
-                    fieldsToInclude.push("type", "value", "dependencies", "id", "updateAvailable", "version", "poolId", "node", "dataModelId", "dataPool", "datamodels");
+                    fieldsToInclude.push("type", "value", "dependencies", "updateAvailable", "version", "poolId", "node", "dataModelId", "dataPool", "datamodels");
                     const unPublishedNodes = nodesListToExport.filter(node => !node.activatedDraftId);
                     let publishedNodes = nodesListToExport.filter(node => node.activatedDraftId);
                     publishedNodes = yield this.getNodesWithActiveVersion(publishedNodes);

package/core/utils/version.js

@@ -11,7 +11,7 @@
     Object.defineProperty(exports, "__esModule", { value: true });
     exports.VersionUtils = void 0;
     // tslint:disable-next-line:no-var-requires
-    const { version } = require("../../../package.json");
+    const { version } = require("./../../package.json");
     class VersionUtils {
         static getCurrentCliVersion() {
             return version;

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@celonis/content-cli",
-  "version": "1.0.0",
-  "description": "CLI Tool to help manage content in Celonis EMS",
+  "version": "1.0.4",
+  "description": "CLI Tool to help manage content in Celonis Platform",
   "main": "content-cli.js",
   "bin": {
-    "content-cli": "./dist/content-cli.js"
+    "content-cli": "./content-cli.js"
   },
   "author": "Celonis SE",
   "license": "MIT",