Running into a weird issue with the genesyscloud_routing_queue resource. Every time I run terraform plan, it detects drift on the name attribute, even though the value hasn’t changed in my code. The state file seems out of sync with the actual platform resource, but I can’t update the state because of a lock.
Here is the resource block:
resource "genesyscloud_routing_queue" "support_queue" {
name = "Support Tier 1"
description = "Main support queue"
acd_skill {
name = "English"
priority = 1
}
}
When I try to run terraform refresh, I get this error:
Error: Error acquiring the state lock
Lock Info:
ID: 8f3a9c2b-1234-5678-90ab-cdef12345678
Path: terraform.tfstate
Operation: OperationTypeApply
Who: user@host
Version: 1.5.0
Created: 2024-05-20 14:30:00 +0000 UTC
Info:
The lock was created during a failed apply last week. I tried using terraform force-unlock <lock_id>, but it fails with a 404 Not Found from the backend. The backend is S3 with DynamoDB for state locking. I checked the DynamoDB table and the item exists, but the lock ID in the table doesn’t match the one Terraform is complaining about.
I also tried deleting the lock item directly in DynamoDB, but Terraform still sees the lock. It’s like the local cache or the session is holding onto an old reference.
The drift is specifically on the name field. The API returns the name as “Support Tier 1” but Terraform thinks it’s different. I’ve verified the API response using Postman and the name matches exactly.
Any ideas on how to clear this stale lock without losing state? I don’t want to just delete the state file and start over because we have a lot of resources linked to this queue. Also, why is the name showing as drifted if the API response is correct? Is there a normalization issue in the provider?