fix rename --config-file to --config and --config to --inline-config in cm:stacks:migration by cs-raj · Pull Request #251 · contentstack/cli-plugins

cs-raj · 2026-06-29T12:11:38Z

What

Renamed two flags in cm:stacks:migration to make --config consistent across all stack commands.

Old	New	Purpose
`--config-file <path>`	`--config <path>` / `-c <path>`	Path to a JSON configuration file
`--config <key:val>`	`--inline-config <key:val>`	Inline key-value pairs on the CLI

Why

--config meant different things depending on which command you ran:

cm:stacks:clone → file path
cm:stacks:export → file path
cm:stacks:import → file path
cm:stacks:migration → inline key-value pairs ← inconsistent

A user who learned --config on export/import would pass a file path to migration and get unexpected behaviour with no error or warning. Since CLI v2 is already a breaking release, this is the right window to fix it cleanly.

Migration Guide

# Before
csdx cm:migration --config-file ./config.json --file-path ./script.ts
csdx cm:migration --config key1:val1 key2:val2 --file-path ./script.ts
# After
csdx cm:migration --config ./config.json --file-path ./script.ts
csdx cm:migration --inline-config key1:val1 key2:val2 --file-path ./script.ts

Files Changed

cli-plugins/packages/contentstack-migration/src/commands/cm/stacks/migration.ts
cli-plugins/packages/contentstack-migration/README.md
cli/packages/contentstack/README.md (aggregated main CLI README)

…in cm:stacks:migration

github-actions · 2026-06-29T12:59:37Z

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Threshold	Result
🔴 Critical Severity	10	✅ Passed
🟠 High Severity	25	✅ Passed
🟡 Medium Severity	0	✅ Passed
🔵 Low Severity	0	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	SLA Threshold (with/no fixes)	Status
🔴 Critical	15 / 30 days	✅ Passed
🟠 High	30 / 120 days	✅ Passed
🟡 Medium	90 / 365 days	✅ Passed
🔵 Low	180 / 365 days	✅ Passed

✅ BUILD PASSED - All security checks passed

github-actions · 2026-06-29T13:05:38Z

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Without fixes	Threshold	Result
🔴 Critical Severity	0	10	✅ Passed
🟠 High Severity	0	25	✅ Passed
🟡 Medium Severity	1	500	✅ Passed
🔵 Low Severity	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	15 / 30 days	✅ Passed
🟠 High	0	30 / 120 days	✅ Passed
🟡 Medium	1	90 / 365 days	⚠️ Warning
🔵 Low	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

Critical without fixes: 0
High without fixes: 0
Medium without fixes: 1
Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

github-actions · 2026-06-30T05:46:39Z

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Without fixes	Threshold	Result
🔴 Critical Severity	0	10	✅ Passed
🟠 High Severity	60	25	✅ Passed
🟡 Medium Severity	1	500	✅ Passed
🔵 Low Severity	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	15 / 30 days	✅ Passed
🟠 High	0	30 / 120 days	✅ Passed
🟡 Medium	1	90 / 365 days	⚠️ Warning
🔵 Low	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

Critical without fixes: 0
High without fixes: 60
Medium without fixes: 1
Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

snyk-io · 2026-08-06T07:38:31Z

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

github-actions · 2026-08-06T07:39:14Z

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Without fixes	Threshold	Result
🔴 Critical Severity	0	10	✅ Passed
🟠 High Severity	0	25	✅ Passed
🟡 Medium Severity	1	500	✅ Passed
🔵 Low Severity	0	1000	✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	15 / 30 days	✅ Passed
🟠 High	0	30 / 120 days	✅ Passed
🟡 Medium	1	90 / 365 days	⚠️ Warning
🔵 Low	0	180 / 365 days	✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

Critical without fixes: 0
High without fixes: 0
Medium without fixes: 1
Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

github-actions · 2026-08-06T12:47:56Z

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Threshold	Result
🔴 Critical Severity	10	✅ Passed
🟠 High Severity	25	✅ Passed
🟡 Medium Severity	500	✅ Passed
🔵 Low Severity	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	SLA Threshold (with/no fixes)	Status
🔴 Critical	15 / 30 days	✅ Passed
🟠 High	30 / 120 days	✅ Passed
🟡 Medium	90 / 365 days	✅ Passed
🔵 Low	180 / 365 days	✅ Passed

✅ BUILD PASSED - All security checks passed

fix rename --config-file to --config and --config to --inline-config in cm:stacks:migration

fix rename --config-file to --config and --config to --inline-config …
d2e2740
…in cm:stacks:migration

cs-raj requested a review from a team as a code owner June 29, 2026 12:11

cs-raj requested review from harshitha-cstk and netrajpatel June 29, 2026 12:11

Merge branch 'v2-dev' into fix/DX-3921
8c6f3dc

lock file update
cf65e49

Merge branch 'v2-dev' into fix/DX-3921
2189b1b

cs-raj added 2 commits August 6, 2026 13:07

Merge branch 'v2-dev' into fix/DX-3921
7c9ea61

Lock file update
b9e5104

harshitha-cstk previously approved these changes Aug 6, 2026
View reviewed changes

Merge branch 'v2-dev' into fix/DX-3921
f6097f0

harshitha-cstk dismissed their stale review via f6097f0August 6, 2026 12:47

harshitha-cstk approved these changes Aug 6, 2026
View reviewed changes

cs-raj merged commit 1254c29 into v2-devAug 6, 2026
11 checks passed

cs-raj deleted the fix/DX-3921 branch August 6, 2026 15:39

naman-contentstack pushed a commit that referenced this pull request Aug 7, 2026
Merge pull request#251from contentstack/fix/DX-3921
524937a
fix rename --config-file to --config and --config to --inline-config in cm:stacks:migration

Navigation Menu

Uh oh!

fix rename --config-file to --config and --config to --inline-config in cm:stacks:migration - #251

fix rename --config-file to --config and --config to --inline-config in cm:stacks:migration#251
cs-raj merged 7 commits into
v2-devfrom
fix/DX-3921

cs-raj commented Jun 29, 2026

Uh oh!

github-actionsBot commented Jun 29, 2026

Uh oh!

github-actionsBot commented Jun 29, 2026

Uh oh!

github-actionsBot commented Jun 30, 2026

Uh oh!

snyk-ioBot commented Aug 6, 2026•
edited
Loading

Uh oh!

github-actionsBot commented Aug 6, 2026

Uh oh!

github-actionsBot commented Aug 6, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

cs-raj commented Jun 29, 2026

What

Why

Migration Guide

Files Changed

Uh oh!

github-actionsBot commented Jun 29, 2026

🔒 Security Scan Results

⏱️ SLA Breach Summary

Uh oh!

github-actionsBot commented Jun 29, 2026

🔒 Security Scan Results

⏱️ SLA Breach Summary

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

Uh oh!

github-actionsBot commented Jun 30, 2026

🔒 Security Scan Results

⏱️ SLA Breach Summary

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

Uh oh!

snyk-ioBot commented Aug 6, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Snyk checks have passed. No issues have been found so far.

Uh oh!

github-actionsBot commented Aug 6, 2026

🔒 Security Scan Results

⏱️ SLA Breach Summary

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

Uh oh!

github-actionsBot commented Aug 6, 2026

🔒 Security Scan Results

⏱️ SLA Breach Summary

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

snyk-ioBot commented Aug 6, 2026•
edited
Loading