Running into a bit of a headache with our TF pipeline. We’ve got a massive genesyscloud_routing_queue resource that’s showing up with drift in terraform plan. Usually, I’d just run an apply to fix it, but now I’m hitting a state lock error that won’t go away.
Here’s the error:
Error: Error acquiring the state lock
on main.tf line 1, in resource "genesyscloud_routing_queue" "main_queue":
1: resource "genesyscloud_routing_queue" "main_queue" {
Lock Info:
ID: 12345678-1234-1234-1234-123456789012
Path: gs://my-tf-state-bucket/terraform.tfstate
Operation: OperationTypeApply
Who: ci-runner-1@jenkins
Version: 1.35.0
Created: 2023-10-27T14:22:05Z
Info:
The CI job that acquired the lock failed halfway through an apply, so the lock is stuck. I know I can force unlock it, but I want to make sure I’m not stomping on something. The queue is live and handling calls right now.
Is it safe to run terraform force-unlock in this scenario? Or is there a way to manually clear the drift without unlocking? We’re using the Genesys Cloud Terraform provider v1.35.0.
Here’s a snippet of the resource causing issues:
resource "genesyscloud_routing_queue" "main_queue" {
name = "Priority Support"
description = "High priority queue"
enabled = true
acd_settings {
service_level_percentage = 0.80
service_level_wait_seconds = 20
}
}
Any advice on handling this safely?