From 0741760f3f9f74ff92b80483027e32aca676a384 Mon Sep 17 00:00:00 2001 From: kmchau Date: Wed, 24 Aug 2022 14:37:11 +0800 Subject: [PATCH] Update init.mdx Suspect it is a typo... --- website/docs/cli/commands/init.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/cli/commands/init.mdx b/website/docs/cli/commands/init.mdx index 05e679b2ef..c197fed636 100644 --- a/website/docs/cli/commands/init.mdx +++ b/website/docs/cli/commands/init.mdx @@ -85,7 +85,7 @@ The `-migrate-state` option will attempt to copy existing state to the new backend, and depending on what changed, may result in interactive prompts to confirm migration of workspace states. The `-force-copy` option suppresses these prompts and answers "yes" to the migration questions. This implies -`-migrate-state`. +`-reconfigure`. The `-reconfigure` option disregards any existing configuration, preventing migration of any existing state.