From 493973d6da3da95abf747e19e28155ff7bb815d2 Mon Sep 17 00:00:00 2001 From: Christopher Hackett Date: Sat, 18 Mar 2023 20:22:31 +0000 Subject: [PATCH] Correct docs on Configuration Directory The option was removed in v0.15 and so is no-longer "plan[ed]" https://newreleases.io/project/github/hashicorp/terraform/release/v0.15.0 --- website/docs/cli/commands/init.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/cli/commands/init.mdx b/website/docs/cli/commands/init.mdx index 4fe045a1fb..95f75ec96d 100644 --- a/website/docs/cli/commands/init.mdx +++ b/website/docs/cli/commands/init.mdx @@ -189,8 +189,8 @@ Terraform v0.13 and earlier also accepted a directory path in place of the plan file argument to `terraform apply`, in which case Terraform would use that directory as the root module instead of the current working directory. -That usage is still supported in Terraform v0.14, but is now deprecated and we -plan to remove it in Terraform v0.15. If your workflow relies on overriding +That usage is still supported in Terraform v0.14, but is now deprecated and removed in +Terraform v0.15. If your workflow relies on overriding the root module directory, use [the `-chdir` global option](/terraform/cli/commands#switching-working-directory-with-chdir) instead, which works across all commands and makes Terraform consistently look