2017-02-13 20:15:40 +01:00
|
|
|
---
|
|
|
|
|
layout: "docs"
|
|
|
|
|
page_title: "Command: force-unlock"
|
|
|
|
|
sidebar_current: "docs-commands-force-unlock"
|
|
|
|
|
description: |-
|
|
|
|
|
The `terraform force-unlock` manually unlocks the Terraform state
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# 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
|
|
|
|
|
|
2017-07-18 18:02:29 +02:00
|
|
|
Usage: terraform force-unlock 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:
|
|
|
|
|
|
|
|
|
|
* `-force` - Don't ask for input for unlock confirmation.
|
