Update internal/command/clistate to use OpenTF in user-provided strings. (#72)

Signed-off-by: Jakub Martin <kubam@spacelift.io>
This commit is contained in:
Kuba Martin 2023-08-22 16:51:22 +02:00 committed by GitHub
parent 9ee1c7d178
commit 72fd4f9ce9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -23,18 +23,18 @@ const (
LockThreshold = 400 * time.Millisecond LockThreshold = 400 * time.Millisecond
LockErrorMessage = `Error message: %s LockErrorMessage = `Error message: %s
Terraform acquires a state lock to protect the state from being written OpenTF acquires a state lock to protect the state from being written
by multiple users at the same time. Please resolve the issue above and try by multiple users at the same time. Please resolve the issue above and try
again. For most commands, you can disable locking with the "-lock=false" again. For most commands, you can disable locking with the "-lock=false"
flag, but this is not recommended.` flag, but this is not recommended.`
UnlockErrorMessage = `Error message: %s UnlockErrorMessage = `Error message: %s
Terraform acquires a lock when accessing your state to prevent others OpenTF acquires a lock when accessing your state to prevent others
running Terraform to potentially modify the state at the same time. An running OpenTF to potentially modify the state at the same time. An
error occurred while releasing this lock. This could mean that the lock error occurred while releasing this lock. This could mean that the lock
did or did not release properly. If the lock didn't release properly, did or did not release properly. If the lock didn't release properly,
Terraform may not be able to run future commands since it'll appear as if OpenTF may not be able to run future commands since it'll appear as if
the lock is held. the lock is held.
In this scenario, please call the "force-unlock" command to unlock the In this scenario, please call the "force-unlock" command to unlock the