1.5.3 • Published 13 days ago
@contentstack/cli-migration v1.5.3
@contentstack/cli-migration
The Contentstack CLI’s “Migration” plugin allows developers to automate the content migration process and easily migrate your content from your system to Contentstack.
Usage
$ npm install -g @contentstack/cli-migration
$ csdx COMMAND
running command...
$ csdx (--version)
@contentstack/cli-migration/1.5.1 darwin-arm64 node-v20.8.0
$ csdx --help [COMMAND]
USAGE
$ csdx COMMAND
...
Commands
csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]
csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]
csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]
Contentstack migration script.
USAGE
$ csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>]
[--config <value>] [--multiple]
FLAGS
-B, --branch=<value> Use this flag to add the branch name where you want to perform the migration.
-a, --alias=<value> Use this flag to add the management token alias.
-k, --stack-api-key=<value> With this flag add the API key of your stack.
--config=<value>... [optional] inline configuration, <key1>:<value1>
--config-file=<value> [optional] Path of the JSON configuration file
--file-path=<value> Use this flag to provide the path of the file of the migration script provided by the
user.
--multiple This flag helps you to migrate multiple content files in a single instance.
DESCRIPTION
Contentstack migration script.
ALIASES
$ csdx cm:migration
EXAMPLES
$ csdx cm:migration --file-path <migration/script/file/path> -k <api-key>
$ csdx cm:migration --file-path <migration/script/file/path> -k <api-key> --branch <target branch name>
$ csdx cm:migration --config <key1>:<value1> <key2>:<value2> ... --file-path <migration/script/file/path>
$ csdx cm:migration --config-file <path/to/json/config/file> --file-path <migration/script/file/path>
$ csdx cm:migration --multiple --file-path <migration/scripts/dir/path>
$ csdx cm:migration --alias --file-path <migration/script/file/path> -k <api-key>
csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>] [--config <value>] [--multiple]
Contentstack migration script.
USAGE
$ csdx cm:stacks:migration [-k <value>] [-a <value>] [--file-path <value>] [--branch <value>] [--config-file <value>]
[--config <value>] [--multiple]
FLAGS
-B, --branch=<value> Use this flag to add the branch name where you want to perform the migration.
-a, --alias=<value> Use this flag to add the management token alias.
-k, --stack-api-key=<value> With this flag add the API key of your stack.
--config=<value>... [optional] inline configuration, <key1>:<value1>
--config-file=<value> [optional] Path of the JSON configuration file
--file-path=<value> Use this flag to provide the path of the file of the migration script provided by the
user.
--multiple This flag helps you to migrate multiple content files in a single instance.
DESCRIPTION
Contentstack migration script.
ALIASES
$ csdx cm:migration
EXAMPLES
$ csdx cm:migration --file-path <migration/script/file/path> -k <api-key>
$ csdx cm:migration --file-path <migration/script/file/path> -k <api-key> --branch <target branch name>
$ csdx cm:migration --config <key1>:<value1> <key2>:<value2> ... --file-path <migration/script/file/path>
$ csdx cm:migration --config-file <path/to/json/config/file> --file-path <migration/script/file/path>
$ csdx cm:migration --multiple --file-path <migration/scripts/dir/path>
$ csdx cm:migration --alias --file-path <migration/script/file/path> -k <api-key>
See code: src/commands/cm/stacks/migration.js
Points to remember
- Currently, you can pass a custom schema to the createField method to migrate group fields.
- You can migrate global fields by creating an SDK instance and adding it to content types using the createField method.
- Currently, you can migrate entries by creating an SDK instance to create/update/delete entries for your content type.
1.5.3
13 days ago
1.5.2
27 days ago
1.5.1
1 month ago
1.5.0
2 months ago
1.4.2
4 months ago
1.4.1
5 months ago
1.4.0
5 months ago
1.3.10
9 months ago
1.3.13
7 months ago
1.3.14
6 months ago
1.3.11
8 months ago
1.3.12
8 months ago
1.3.15
6 months ago
1.3.9
10 months ago
1.3.8
10 months ago
1.3.7
11 months ago
1.3.6
11 months ago
1.3.5
11 months ago
1.3.4
11 months ago
1.3.3
12 months ago
1.3.2
12 months ago
1.3.1
1 year ago
1.2.0
1 year ago
1.3.0
1 year ago
1.1.0
1 year ago
1.0.2
1 year ago
1.0.4
1 year ago
1.0.3
1 year ago
1.0.1
2 years ago
1.0.0
2 years ago
0.1.1-beta.3
2 years ago
0.1.1-beta.2
2 years ago
0.1.1-beta.1
2 years ago