IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

Remove use of RUM acronymn in workspace delete docs

Browse Source
This commit is contained in:
Jarrett Spiker 2022-11-22 15:10:58 -05:00
parent f5a424e65d
commit 1e1312fb78
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/docs/cli/commands/workspace/delete.mdx
View File

@ -17,12 +17,10 @@ To delete a workspace, it must already exist, it must not be tracking resources,
and it must not be your current workspace. If the workspace is tracking resources,
Terraform will not allow you to delete it unless the `-force` flag is specified.
Workspaces with resources under management (RUM) are workspaces which manage resources that physically exist.
This means that the workspace has a non-empty state.
Additionally, different [backends](/language/settings/backends/configuration#backend-types) may implement other
restrictions on whether a workspace is considered to have RUM, such as whether the workspace is locked.
restrictions on whether a workspace is considered safe to delete without the `-force` flag, such as whether the workspace is locked.
If you delete a workspace with resources under management (via `-force`), then resources
If you delete a workspace which is tracking resources (via `-force`), then resources
may become "dangling". These are resources that physically exist but that
Terraform can no longer manage. This is sometimes preferred: you may want
Terraform to stop managing resources, so they can be managed some other way.
@ -31,7 +29,7 @@ from getting into this situation.
The command-line flags are all optional. The only supported flags are:
* `-force` - Delete the workspace even if it has resources under management. After deletion, Terraform can no longer track or manage the workspace's infrastructure. Defaults to false.
* `-force` - Delete the workspace even if it is tracking resources. After deletion, Terraform can no longer track or manage the workspace's infrastructure. Defaults to false.
* `-lock=false` - Don't hold a state lock during the operation. This is
dangerous if others might concurrently run commands against the same
workspace.