@contentstack/cli 1.34.0 → 1.35.0

package/README.md

@@ -18,7 +18,7 @@ $ npm install -g @contentstack/cli
 $ csdx COMMAND
 running command...
 $ csdx (--version|-v)
-@contentstack/cli/1.34.0 linux-x64 node-v18.20.5
+@contentstack/cli/1.35.0 linux-x64 node-v18.20.6
 $ csdx --help [COMMAND]
 USAGE
   $ csdx COMMAND
@@ -2375,27 +2375,37 @@ EXAMPLES
 
 ## `csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]`
 
-Import content from a stack
+Helps to generate mappers and backup folder for importing (overwriting) specific modules
 
 ```
 USAGE
   $ csdx cm:import-setup cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]
 
 FLAGS
-  -a, --alias=<value>          alias of the management token
-  -d, --data-dir=<value>       path and location where data is stored
+  -B, --branch=<value>         The name of the branch where you want to import your content. If you don't mention the
+                               branch name, then by default the content will be imported to the main branch.
+  -a, --alias=<value>          The management token of the destination stack where you will import the content.
+  -d, --data-dir=<value>       The path or the location in your file system where the content, you intend to import, is
+                               stored. For example, -d "C:\Users\Name\Desktop\cli\content". If the export folder has
+                               branches involved, then the path should point till the particular branch. For example,
+                               “-d "C:\Users\Name\Desktop\cli\content\branch_name"
   -k, --stack-api-key=<value>  API key of the target stack
-      --modules=<option>       [optional] specific module name
-                               <options: content-types|entries|both>
+      --module=<option>...     [optional] Specify the modules/module to import into the target stack. currently options
+                               are global-fields, content-types, entries
+                               <options: global-fields|content-types|entries>
 
 DESCRIPTION
-  Import content from a stack
+  Helps to generate mappers and backup folder for importing (overwriting) specific modules
 
 ALIASES
   $ csdx cm:import-setup
 
 EXAMPLES
-  $ csdx cm:stacks:import-setup --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
+  $ csdx cm:stacks:import-setup --stack-api-key <target_stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
+
+  $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name>
+
+  $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name> -b <branch_name>
 ```
 
 ## `csdx cm:migrate-rte`
@@ -2858,27 +2868,37 @@ _See code: [@contentstack/cli-cm-import](https://github.com/contentstack/cli/blo
 
 ## `csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]`
 
-Import content from a stack
+Helps to generate mappers and backup folder for importing (overwriting) specific modules
 
 ```
 USAGE
   $ csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]
 
 FLAGS
-  -a, --alias=<value>          alias of the management token
-  -d, --data-dir=<value>       path and location where data is stored
+  -B, --branch=<value>         The name of the branch where you want to import your content. If you don't mention the
+                               branch name, then by default the content will be imported to the main branch.
+  -a, --alias=<value>          The management token of the destination stack where you will import the content.
+  -d, --data-dir=<value>       The path or the location in your file system where the content, you intend to import, is
+                               stored. For example, -d "C:\Users\Name\Desktop\cli\content". If the export folder has
+                               branches involved, then the path should point till the particular branch. For example,
+                               “-d "C:\Users\Name\Desktop\cli\content\branch_name"
   -k, --stack-api-key=<value>  API key of the target stack
-      --modules=<option>       [optional] specific module name
-                               <options: content-types|entries|both>
+      --module=<option>...     [optional] Specify the modules/module to import into the target stack. currently options
+                               are global-fields, content-types, entries
+                               <options: global-fields|content-types|entries>
 
 DESCRIPTION
-  Import content from a stack
+  Helps to generate mappers and backup folder for importing (overwriting) specific modules
 
 ALIASES
   $ csdx cm:import-setup
 
 EXAMPLES
-  $ csdx cm:stacks:import-setup --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
+  $ csdx cm:stacks:import-setup --stack-api-key <target_stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
+
+  $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name>
+
+  $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name> -b <branch_name>
 ```
 
 _See code: [@contentstack/cli-cm-import-setup](https://github.com/contentstack/cli/blob/main/packages/contentstack-import-setup/src/commands/cm/stacks/import-setup.ts)_
@@ -3581,8 +3601,9 @@ Launch related operations
 USAGE
   $ csdx launch [--type GitHub|FileUpload] [--framework Gatsby|NextJs|CRA (Create React App)|CSR
     (Client-Side Rendered)|Angular|VueJs|Other] [--org <value>] [-n <value>] [-e <value>] [--branch <value>]
-    [--build-command <value>] [--out-dir <value>] [--variable-type Import variables from a stack|Manually add custom
-    variables to the list|Import variables from the local env file] [-a <value>] [--env-variables <value>]
+    [--build-command <value>] [--out-dir <value>] [--server-command <value>] [--variable-type Import variables from a
+    stack|Manually add custom variables to the list|Import variables from the local env file] [-a <value>]
+    [--env-variables <value>] [--redeploy-latest] [--redeploy-last-upload]
 
 FLAGS
   -a, --alias=<value>           [optional] Alias (name) for the delivery token.
@@ -3597,6 +3618,9 @@ FLAGS
                                 Rendered)|Angular|VueJs|Other>
       --org=<value>             [optional] Provide the organization UID to create a new project or deployment.
       --out-dir=<value>         [optional] Output Directory.
+      --redeploy-last-upload    [optional] Redeploy with last file upload
+      --redeploy-latest         [optional] Redeploy latest commit/code
+      --server-command=<value>  [optional] Server Command.
       --type=<option>           [optional] Type of adapters. <options: GitHub|FileUpload>
                                 <options: GitHub|FileUpload>
       --variable-type=<option>  [optional] Provide a variable type. <options: Import variables from a stack|Manually add
@@ -3618,10 +3642,16 @@ EXAMPLES
 
   $ csdx launch --data-dir <path/of/current/working/dir> --type <options: GitHub|FileUpload>
 
+  $ csdx launch --data-dir <path/of/current/working/dir> --redeploy-latest
+
+  $ csdx launch --data-dir <path/of/current/working/dir> --redeploy-latest --redeploy-last-upload
+
   $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload>
 
   $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value>
 
+  $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value> --server-command=<value>
+
   $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value> --variable-type="Import variables from a stack" --alias=<value>
 
   $ csdx launch --config <path/to/launch/config/file> --type <options: GitHub|FileUpload> --name=<value> --environment=<value> --branch=<value> --build-command=<value> --framework=<option> --org=<value> --out-dir=<value> --variable-type="Manually add custom variables to the list" --env-variables="APP_ENV:prod, TEST_ENV:testVal"
@@ -3867,7 +3897,7 @@ EXAMPLES
   $ csdx plugins
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.26/src/commands/plugins/index.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.30/src/commands/plugins/index.ts)_
 
 ## `csdx plugins:add PLUGIN`
 
@@ -3941,7 +3971,7 @@ EXAMPLES
   $ csdx plugins:inspect myplugin
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.26/src/commands/plugins/inspect.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.30/src/commands/plugins/inspect.ts)_
 
 ## `csdx plugins:install PLUGIN`
 
@@ -3990,7 +4020,7 @@ EXAMPLES
     $ csdx plugins:install someuser/someplugin
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.26/src/commands/plugins/install.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.30/src/commands/plugins/install.ts)_
 
 ## `csdx plugins:link PATH`
 
@@ -4021,7 +4051,7 @@ EXAMPLES
   $ csdx plugins:link myplugin
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.26/src/commands/plugins/link.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.30/src/commands/plugins/link.ts)_
 
 ## `csdx plugins:remove [PLUGIN]`
 
@@ -4062,7 +4092,7 @@ FLAGS
   --reinstall  Reinstall all plugins after uninstalling.
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.26/src/commands/plugins/reset.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.30/src/commands/plugins/reset.ts)_
 
 ## `csdx plugins:uninstall [PLUGIN]`
 
@@ -4090,7 +4120,7 @@ EXAMPLES
   $ csdx plugins:uninstall myplugin
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.26/src/commands/plugins/uninstall.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.30/src/commands/plugins/uninstall.ts)_
 
 ## `csdx plugins:unlink [PLUGIN]`
 
@@ -4134,7 +4164,7 @@ DESCRIPTION
   Update installed plugins.
 ```
 
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.26/src/commands/plugins/update.ts)_
+_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v5.4.30/src/commands/plugins/update.ts)_
 
 ## `csdx tokens`
 

package/oclif.manifest.json

@@ -1,4 +1,4 @@
 {
-  "version": "1.34.0",
+  "version": "1.35.0",
   "commands": {}
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@contentstack/cli",
   "description": "Command-line tool (CLI) to interact with Contentstack",
-  "version": "1.34.0",
+  "version": "1.35.0",
   "author": "Contentstack",
   "bin": {
     "csdx": "./bin/run.js"
@@ -31,7 +31,7 @@
     "@contentstack/cli-cm-export": "~1.14.1",
     "@contentstack/cli-cm-export-to-csv": "~1.7.3",
     "@contentstack/cli-cm-import": "~1.19.3",
-    "@contentstack/cli-cm-import-setup": "1.0.0-beta.1",
+    "@contentstack/cli-cm-import-setup": "1.0.0",
     "@contentstack/cli-cm-migrate-rte": "~1.4.20",
     "@contentstack/cli-cm-seed": "~1.10.0",
     "@contentstack/cli-command": "~1.3.2",