mirror of
https://github.com/opentffoundation/opentf.git
synced 2026-02-25 14:00:57 -05:00
4d665a0091
* Initial renaming, rewriting and cleaning up wave for the CLI docs. Signed-off-by: Jakub Martin <kubam@spacelift.io> * More renaming. Signed-off-by: Jakub Martin <kubam@spacelift.io> * More renaming. Signed-off-by: Jakub Martin <kubam@spacelift.io> * More renaming. Signed-off-by: Jakub Martin <kubam@spacelift.io> * Remove tutorial references. Signed-off-by: Jakub Martin <kubam@spacelift.io> * Post-review fixes. Signed-off-by: Jakub Martin <kubam@spacelift.io> --------- Signed-off-by: Jakub Martin <kubam@spacelift.io>
31 lines
924 B
Plaintext
31 lines
924 B
Plaintext
---
|
|
page_title: 'Command: force-unlock'
|
|
description: >-
|
|
The opentf force-unlock command unlocks the state for a configuration. It
|
|
does not modify your infrastructure.
|
|
---
|
|
|
|
# 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
|
|
|
|
Usage: `opentf 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.
|