terraform/website/docs/cli/commands/state/rm.mdx

136 lines
4.9 KiB
Plaintext
Raw Permalink Normal View History

---
2022-01-04 20:58:31 +01:00
page_title: 'Command: state rm'
2021-12-15 03:41:17 +01:00
description: >-
The `terraform state rm` command removes bindings from the Terraform state,
causing Terraform to "forget about" existing objects.
---
# Command: state rm
2021-12-15 03:41:17 +01:00
The main function of [Terraform state](/language/state) is
to track the bindings between resource instance addresses in your configuration
and the remote objects they represent. Normally Terraform automatically
updates the state in response to actions taken when applying a plan, such as
2021-10-02 11:15:51 +02:00
removing a binding for a remote object that has now been deleted.
You can use `terraform state rm` in the less common situation where you wish
to remove a binding to an existing remote object without first destroying it,
which will effectively make Terraform "forget" the object while it continues
to exist in the remote system.
## Usage
Usage: `terraform state rm [options] ADDRESS...`
Terraform will search the state for any instances matching the given
2021-12-15 03:41:17 +01:00
[resource address](/cli/state/resource-addressing), and remove
the record of each one so that Terraform will no longer be tracking the
corresponding remote objects.
This means that although the objects will still continue to exist in the
remote system, a subsequent
2021-12-15 03:41:17 +01:00
[`terraform plan`](/cli/commands/plan)
will include an action to create a new object for each of the "forgotten"
instances. Depending on the constraints imposed by the remote system, creating
those objects might fail if their names or other identifiers conflict with
the old objects still present.
This command also accepts the following options:
2021-12-21 23:19:05 +01:00
- `-dry-run` - Report all of the resource instances that match the given
address without actually "forgetting" any of them.
2021-12-21 23:19:05 +01:00
- `-lock=false` - Don't hold a state lock during the operation. This is
2021-12-15 03:41:17 +01:00
dangerous if others might concurrently run commands against the same
workspace.
2021-12-21 23:19:05 +01:00
- `-lock-timeout=DURATION` - Unless locking is disabled with `-lock=false`,
instructs Terraform to retry acquiring a lock for a period of time before
returning an error. The duration syntax is a number followed by a time
unit letter, such as "3s" for three seconds.
2021-12-21 23:19:05 +01:00
For configurations using the [Terraform Cloud CLI integration](/cli/cloud) or the [`remote` backend](/language/settings/backends/remote)
only, `terraform state rm`
also accepts the option
2021-12-21 23:37:35 +01:00
[`-ignore-remote-version`](/cli/cloud/command-line-arguments#ignore-remote-version).
For configurations using
2021-12-15 03:41:17 +01:00
[the `local` state rm](/language/settings/backends/local) only,
`terraform state rm` also accepts the legacy options
2021-12-15 03:41:17 +01:00
[`-state`, `-state-out`, and `-backup`](/language/settings/backends/local#command-line-arguments).
backend: Validate remote backend Terraform version When using the enhanced remote backend, a subset of all Terraform operations are supported. Of these, only plan and apply can be executed on the remote infrastructure (e.g. Terraform Cloud). Other operations run locally and use the remote backend for state storage. This causes problems when the local version of Terraform does not match the configured version from the remote workspace. If the two versions are incompatible, an `import` or `state mv` operation can cause the remote workspace to be unusable until a manual fix is applied. To prevent this from happening accidentally, this commit introduces a check that the local Terraform version and the configured remote workspace Terraform version are compatible. This check is skipped for commands which do not write state, and can also be disabled by the use of a new command-line flag, `-ignore-remote-version`. Terraform version compatibility is defined as: - For all releases before 0.14.0, local must exactly equal remote, as two different versions cannot share state; - 0.14.0 to 1.0.x are compatible, as we will not change the state version number until at least Terraform 1.1.0; - Versions after 1.1.0 must have the same major and minor versions, as we will not change the state version number in a patch release. If the two versions are incompatible, a diagnostic is displayed, advising that the error can be suppressed with `-ignore-remote-version`. When this flag is used, the diagnostic is still displayed, but as a warning instead of an error. Commands which will not write state can assert this fact by calling the helper `meta.ignoreRemoteBackendVersionConflict`, which will disable the checks. Those which can write state should instead call the helper `meta.remoteBackendVersionCheck`, which will return diagnostics for display. In addition to these explicit paths for managing the version check, we have an implicit check in the remote backend's state manager initialization method. Both of the above helpers will disable this check. This fallback is in place to ensure that future code paths which access state cannot accidentally skip the remote version check.
2020-11-13 22:43:56 +01:00
## Example: Remove all Instances of a Resource
The following example will cause Terraform to "forget" all of the instances
of the `packet_device` resource named "worker".
```shell
$ terraform state rm 'packet_device.worker'
```
A resource that doesn't use `count` or `for_each` has only one instance, so
this is also the appropriate syntax to select that single instance.
## Example: Remove all Instances of a Resource in a Module
To select a resource that you've defined in a child module you must specify
the path of that module as part of the resource address:
```shell
$ terraform state rm 'module.foo.packet_device.worker'
```
## Example: Remove all Instances of all Resources in a Module
The following example will cause Terraform to "forget" all of the instances
associated with all resources defined in all instances of the module named
`foo`:
```shell
$ terraform state rm 'module.foo'
```
## Example: Remove a Particular Instance of a Resource using `count`
2021-12-15 03:41:17 +01:00
A resource defined with [the `count` meta-argument](/language/meta-arguments/count)
has multiple instances that are each identified by an integer. You can
select a particular instance by including an explicit index in your given
address:
```shell
$ terraform state rm 'packet_device.worker[0]'
```
Brackets (`[`, `]`) have a special meaning in some shells, so you may need to
quote or escape the address in order to pass it literally to Terraform.
The above shows the typical quoting syntax for Unix-style shells.
## Example: Remove a Particular Instance of a Resource using `for_each`
2021-12-15 03:41:17 +01:00
A resource defined with [the `for_each` meta-argument](/language/meta-arguments/for_each)
has multiple instances that are each identified by an string. You can
select a particular instance by including an explicit key in your given
address.
However, the syntax for strings includes quotes and the quote symbol often
has special meaning in command shells, so you'll need to use the appropriate
quoting and/or escaping syntax for the shell you are using. For example:
Unix-style shells, such as on Linux or macOS:
```shell
$ terraform state rm 'packet_device.worker["example"]'
```
Windows Command Prompt (`cmd.exe`):
```shell
$ terraform state rm packet_device.worker[\"example\"]
```
PowerShell:
```shell
$ terraform state rm 'packet_device.worker[\"example\"]'
```