2017-02-13 20:15:40 +01:00
|
|
|
---
|
2021-11-23 00:47:36 +01:00
|
|
|
page_title: 'Command: force-unlock'
|
|
|
|
|
description: >-
|
|
|
|
|
The terraform force-unlock command unlocks the state for a configuration. It
|
|
|
|
|
does not modify your infrastructure.
|
2017-02-13 20:15:40 +01:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Command: force-unlock
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
## Usage
|
|
|
|
|
|
2020-10-21 23:13:18 +02:00
|
|
|
Usage: `terraform force-unlock [options] LOCK_ID [DIR]`
|
2017-02-13 20:15:40 +01:00
|
|
|
|
|
|
|
|
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:
|
|
|
|
|
|
2021-11-23 00:47:36 +01:00
|
|
|
* `-force` - Don't ask for input for unlock confirmation.
|
