You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
terraform/website/docs/cli/commands/force-unlock.mdx

36 lines
1.6 KiB

---
page_title: terraform force-unlock command reference
description: >-
The `terraform force-unlock` command unlocks the state for a configuration. It
does not modify your infrastructure.
---
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
> [!IMPORTANT]
> **Documentation Update:** Product documentation previously located in `/website` has moved to the [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs) repository, where all product documentation is now centralized. Please make contributions directly to `web-unified-docs`, since changes to `/website` in this repository will not appear on developer.hashicorp.com.
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
# `terraform force-unlock` command
This topic provides reference information about the `terraform force-unlock` command. This command manually unlocks the state for the defined configuration.
This command removes the lock on the state for the current configuration. The behavior of this lock is dependent
on the backend being used. Local state files cannot be unlocked by another
process. The `terraform force-unlock` command does not modify your infrastructure.
## Usage
Usage: `terraform force-unlock [options] LOCK_ID`
Manually unlock the state for the defined configuration.
This will not modify your infrastructure. This command removes the lock on the
state for the current configuration. The behavior of this lock is dependent
on the backend being used. Local state files cannot be unlocked by another
process.
Options:
- `-force` - Don't ask for input for unlock confirmation.