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
|
|
|
|
|
|
main: new global option -chdir
This new option is intended to address the previous inconsistencies where
some older subcommands supported partially changing the target directory
(where Terraform would use the new directory inconsistently) where newer
commands did not support that override at all.
Instead, now Terraform will accept a -chdir command at the start of the
command line (before the subcommand) and will interpret it as a request
to direct all actions that would normally be taken in the current working
directory into the target directory instead. This is similar to options
offered by some other similar tools, such as the -C option in "make".
The new option is only accepted at the start of the command line (before
the subcommand) as a way to reflect that it is a global command (not
specific to a particular subcommand) and that it takes effect _before_
executing the subcommand. This also means it'll be forced to appear before
any other command-specific arguments that take file paths, which hopefully
communicates that those other arguments are interpreted relative to the
overridden path.
As a measure of pragmatism for existing uses, the path.cwd object in
the Terraform language will continue to return the _original_ working
directory (ignoring -chdir), in case that is important in some exceptional
workflows. The path.root object gives the root module directory, which
will always match the overriden working directory unless the user
simultaneously uses one of the legacy directory override arguments, which
is not a pattern we intend to support in the long run.
As a first step down the deprecation path, this commit adjusts the
documentation to de-emphasize the inconsistent old command line arguments,
including specific guidance on what to use instead for the main three
workflow commands, but all of those options remain supported in the same
way as they were before. In a later commit we'll make those arguments
produce a visible deprecation warning in Terraform's output, and then
in an even later commit we'll remove them entirely so that -chdir is the
single supported way to run Terraform from a directory other than the
one containing the root module configuration.
2020-09-02 00:45:12 +02:00
|
|
|
Usage: terraform force-unlock LOCK_ID
|
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.
|