Hey folks,
Running into a weird issue with the Genesys Cloud Terraform provider. I’ve got a genesyscloud_routing_queue resource that’s been sitting in state for months without changes. Suddenly, terraform plan is flagging it for updates, but the drift isn’t logical. It looks like the provider is trying to update the outbound_call configuration even though I haven’t touched that block in the code.
Here’s the relevant snippet:
resource "genesyscloud_routing_queue" "sales_queue" {
name = "Sales Support"
description = "General sales inquiries"
wrap_up_policy = {
type = "IMMEDIATE"
}
# This block hasn't changed in 6 months
outbound_call {
enabled = false
}
}
When I run the plan, I get this diff:
# genesyscloud_routing_queue.sales_queue will be updated in-place
~ resource "genesyscloud_routing_queue" "sales_queue" {
~ outbound_call = [
~ {
~ enabled = true -> false
}
]
... (other unchanged attributes)
}
The thing is, I checked the actual queue in the Genesys UI, and Outbound Calls is definitely disabled. The API response for GET /api/v2/routing/queues/{id} also shows outboundCall.enabled: false. So the real state matches my Terraform code. The drift is coming from the Terraform state file itself, which seems to think the value is true.
I tried running terraform refresh but it didn’t fix the state file. I’m hesitant to do a terraform state rm and re-import because there are other dependencies tied to this queue (like skill groups and user assignments) and I don’t want to break the graph.
Has anyone seen the provider cache stale outbound settings like this? Is there a way to force the provider to re-read the actual API state for just this resource without blowing away the whole state entry? Or am I missing something obvious about how the outbound_call block is serialized?
Thanks!