Running into a headache with the Genesys Cloud Terraform provider (v1.28.0). I’m trying to refactor our setup to use data sources instead of hardcoding IDs, but the name-based lookup for routing queues is acting up.
I’ve got a queue named “Priority_Support_AUS” in the org. When I query it directly via the API (GET /api/v2/routing/queues), it shows up fine with that exact name. But in Terraform, the data source throws a 404.
Here’s the block:
hcl
data "genesyscloud_routing_queue" "priority_aus" {
name = "Priority_Support_Aus"
}
The error is straightforward but unhelpful:
Error: No matching resource was found for data genesyscloud_routing_queue.priority_aus
I’ve checked the casing. I’ve checked for trailing spaces. I even tried using the genesyscloud_routing_queue_search data source with a filter, but that returns an empty list, which is weird because the queue definitely exists.
Is the provider doing a case-sensitive match on the name attribute? Or is there some weird caching issue with the data source lookup? I don’t want to start parsing API responses manually just to get an ID into a variable.