Running into a weird state lock issue when trying to update a routing queue. The plan shows drift on genesyscloud_routing_queue even though the config hasn’t changed. It seems like the state file is locked or out of sync.
Here is the error payload:
Error: Error acquiring the state lock
on main.tf line 1, in provider "genesyscloud":
1: provider "genesyscloud" {
Lock Info:
ID: 1234567890
Path: genesyscloud_routing_queue/main.tf
Operation: OperationTypeApply
Who: @company.com
Version: 1.0.0
Created: 2023-10-25 14:23:45.123456 +0000 UTC
Info:
Terraform 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
again. For most commands, you can disable locking with the "-lock=false"
flag, but this is not recommended.
I’ve tried terraform force-unlock with the ID, but it fails with a 404. The backend is S3 with DynamoDB. The DynamoDB table shows no locks.
Is there a way to clear this via the Genesys API? Or is this a Terraform provider bug? I’ve checked the docs and nothing mentions this specific scenario.