Just noticed that referencing existing Genesys Cloud resources by name via Terraform data sources is behaving unexpectedly in my Go-based infrastructure pipeline. I am building a high-throughput service that relies on specific routing configurations, and I need to dynamically fetch the IDs of existing resources like user queues or business hour schedules to ensure my Terraform state remains consistent with the actual platform state without hardcoding IDs. I am using the genesyscloud provider in Terraform, specifically attempting to use data sources like genesyscloud_routing_queue or genesyscloud_routing_business_hours_schedule to look up resources by their name attribute. However, when I run terraform plan, the data source lookup fails or returns no results, even though I can verify via the Genesys Cloud UI and API that these resources exist and are active. I have tried using the name filter in the data source configuration, but it seems sensitive to case or partial matches, and the documentation is sparse on exact matching behavior. This is causing my Go service, which reads the Terraform output to configure its internal routing logic, to fail with a “resource not found” error during initialization. I need a reliable way to resolve these resources by name programmatically within the Terraform workflow.
Here is a snippet of my current Terraform configuration that is failing:
data "genesyscloud_routing_queue" "my_queue" {
name = "Support Queue Alpha"
}
output "queue_id" {
value = data.genesyscloud_routing_queue.my_queue.id
}
The error message I receive during terraform apply is:
Error: Data source "genesyscloud_routing_queue" not found
I have verified that a queue named “Support Queue Alpha” exists in my Genesys Cloud organization. Is there a specific syntax or attribute I should use to ensure exact name matching? Or is there a better practice for referencing existing resources by name in the Genesys Cloud Terraform provider? I am open to using the Genesys Cloud API directly in my Go code if Terraform data sources are not reliable for this use case, but I prefer to keep the infrastructure definitions in Terraform. Any insights into the expected behavior of these data sources or workarounds would be greatly appreciated.