From 5440d9653b966e28be37a9efed4c842aefe80c3c Mon Sep 17 00:00:00 2001 From: Chris Arcand Date: Wed, 6 Jan 2021 09:53:43 -0600 Subject: [PATCH] [skip-ci] Remove documentation on 'CONFIRM_DESTROY' This variable mechanism was replaced long ago with a explicit `Allow destroy plans` setting on a Terraform Cloud workspace, and no longer does anything: https://www.terraform.io/docs/cloud/workspaces/settings.html#destruction-and-deletion Rather than mention this new mechanism at all though, I've removed the requisite from here entirely - the reason being that a consideration like this is no different from other permission concerns (e.g. "You must have Apply permission on a workspace to `apply`"), and without enumerating _all_ of these here - which doesn't seem appropriate - we just remove this concern entirely. --- website/docs/backends/types/remote.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/backends/types/remote.html.md b/website/docs/backends/types/remote.html.md index 982780923d..275cf6e71a 100644 --- a/website/docs/backends/types/remote.html.md +++ b/website/docs/backends/types/remote.html.md @@ -28,7 +28,7 @@ Currently the remote backend supports the following Terraform commands: - `apply` - `console` (supported in Terraform >= v0.11.12) -- `destroy` (requires manually setting `CONFIRM_DESTROY=1` on the workspace) +- `destroy` - `fmt` - `get` - `graph` (supported in Terraform >= v0.11.12)