@@ -47,7 +47,7 @@ $ npm install -g @contentstack/cli-cm-import-setup
4747$ csdx COMMAND
4848running command...
4949$ csdx (--version)
50- @contentstack/cli-cm-import-setup/1.0.0-beta.1 darwin-arm64 node-v22.8 .0
50+ @contentstack/cli-cm-import-setup/1.0.0 darwin-arm64 node-v22.2 .0
5151$ csdx --help [COMMAND]
5252USAGE
5353 $ csdx COMMAND
@@ -63,52 +63,72 @@ USAGE
6363
6464## ` csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>] `
6565
66- Import content from a stack
66+ Helps to generate mappers and backup folder for importing (overwriting) specific modules
6767
6868```
6969USAGE
7070 $ csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]
7171
7272FLAGS
73- -a, --alias=<value> alias of the management token
74- -d, --data-dir=<value> path and location where data is stored
73+ -B, --branch=<value> The name of the branch where you want to import your content. If you don't mention the
74+ branch name, then by default the content will be imported to the main branch.
75+ -a, --alias=<value> The management token of the destination stack where you will import the content.
76+ -d, --data-dir=<value> The path or the location in your file system where the content, you intend to import, is
77+ stored. For example, -d "C:\Users\Name\Desktop\cli\content". If the export folder has
78+ branches involved, then the path should point till the particular branch. For example,
79+ “-d "C:\Users\Name\Desktop\cli\content\branch_name"
7580 -k, --stack-api-key=<value> API key of the target stack
76- --modules=<option> [optional] specific module name
77- <options: content-types|entries|both>
81+ --module=<option>... [optional] Specify the modules/module to import into the target stack. currently options
82+ are global-fields, content-types, entries
83+ <options: global-fields|content-types|entries>
7884
7985DESCRIPTION
80- Import content from a stack
86+ Helps to generate mappers and backup folder for importing (overwriting) specific modules
8187
8288ALIASES
8389 $ csdx cm:import-setup
8490
8591EXAMPLES
86- $ csdx cm:stacks:import-setup --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
92+ $ csdx cm:stacks:import-setup --stack-api-key <target_stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
93+
94+ $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name>
95+
96+ $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name> -b <branch_name>
8797```
8898
8999## ` csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>] `
90100
91- Import content from a stack
101+ Helps to generate mappers and backup folder for importing (overwriting) specific modules
92102
93103```
94104USAGE
95105 $ csdx cm:stacks:import-setup [-k <value>] [-d <value>] [-a <value>] [--modules <value,value>]
96106
97107FLAGS
98- -a, --alias=<value> alias of the management token
99- -d, --data-dir=<value> path and location where data is stored
108+ -B, --branch=<value> The name of the branch where you want to import your content. If you don't mention the
109+ branch name, then by default the content will be imported to the main branch.
110+ -a, --alias=<value> The management token of the destination stack where you will import the content.
111+ -d, --data-dir=<value> The path or the location in your file system where the content, you intend to import, is
112+ stored. For example, -d "C:\Users\Name\Desktop\cli\content". If the export folder has
113+ branches involved, then the path should point till the particular branch. For example,
114+ “-d "C:\Users\Name\Desktop\cli\content\branch_name"
100115 -k, --stack-api-key=<value> API key of the target stack
101- --modules=<option> [optional] specific module name
102- <options: content-types|entries|both>
116+ --module=<option>... [optional] Specify the modules/module to import into the target stack. currently options
117+ are global-fields, content-types, entries
118+ <options: global-fields|content-types|entries>
103119
104120DESCRIPTION
105- Import content from a stack
121+ Helps to generate mappers and backup folder for importing (overwriting) specific modules
106122
107123ALIASES
108124 $ csdx cm:import-setup
109125
110126EXAMPLES
111- $ csdx cm:stacks:import-setup --stack-api-key <stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
127+ $ csdx cm:stacks:import-setup --stack-api-key <target_stack_api_key> --data-dir <path/of/export/destination/dir> --modules <module_name, module_name>
128+
129+ $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name>
130+
131+ $ csdx cm:stacks:import-setup -k <target_stack_api_key> -d <path/of/export/destination/dir> --modules <module_name, module_name> -b <branch_name>
112132```
113133
114134_ See code: [ src/commands/cm/stacks/import-setup.ts] ( https://github.com/contentstack/cli/blob/main/packages/contentstack-import-setup/src/commands/cm/stacks/import-setup.ts ) _
0 commit comments