I’m trying to import an existing routing queue into my Terraform state, but it’s throwing a 404 every time. I’ve got about 50 queues to bring under management, and the genesyscloud_routing_queue resource seems picky about the ID format.
Here’s the block I’m using:
resource "genesyscloud_routing_queue" "existing_queue" {
name = "Support Tier 1"
description = "Main support queue"
status = "ACTIVE"
}
I’m running the import command like this:
terraform import genesyscloud_routing_queue.existing_queue <queue-id-from-admin-ui>
The ID I’m using is the one from the URL in the Genesys admin console, which looks like a1b2c3d4-e5f6-7890-abcd-ef1234567890. When I run the import, Terraform says:
Error: Error importing object "genesyscloud_routing_queue.existing_queue": resource genesyscloud_routing_queue.existing_queue not found
I’ve double-checked the ID by copying it directly from the browser. I even tried using the genesyscloud provider debug logs to see what API call is being made. It looks like it’s hitting GET /api/v2/routing/queues/<id>, which returns a 200 OK in Postman with the same token and ID. So the resource definitely exists and my auth is fine.
Is there a specific format the import command expects? Maybe the provider is stripping characters or expecting a different ID type? I’ve also tried using the external ID field, but that didn’t work either.
I’m using Terraform 1.5.7 and the genesyscloud provider version 1.28.0. State file is clean, no drift issues yet. Just can’t get the initial import to stick. Feels like I’m missing something obvious about how the provider maps the API response to the state object. Any ideas what’s causing the 404 on the import step specifically?