Step one: The team wants to stop clicking around the Genesys Cloud admin portal to set up new support queues, so we’re trying to push everything through Terraform using the CX as Code provider. We’ve got the basic queue definition working fine, but the skills part is throwing a wrench in the works. The documentation mentions skills inside the genesyscloud_routing_queue resource, but the structure isn’t clicking for me.
Step two: I’m trying to assign a specific skill, say “fraud_review”, to the queue so the routing engine picks it up correctly. Nesting it in the outbound_config block didn’t work, nor did putting it as a top-level attribute. Both approaches fail during the plan phase. Here’s the block I’m wrestling with right now.
resource "genesyscloud_routing_queue" "fraud_queue" {
name = "Fraud Review Queue"
description = "Queue for fraud cases"
skills = [
{
id = "some-guid-here"
}
]
}
Step three: The error message claims the schema is invalid. It says Inappropriate value for attribute "skills": set of object required. I don’t get why it wants a set of objects if I’m just passing a list of IDs. Usually, the REST API accepts an array of strings for skill IDs, so why is the Terraform provider demanding this object structure?
The skill ID is correct, pulled directly from the genesyscloud_routing_skill data source. I’ve verified the GUID matches what’s in the web UI. The rest of the queue config applies without issue, just this attribute kills the run.
Is there a wrapper object I’m missing? The provider docs are pretty sparse on the exact JSON shape for this field. I’ve tried using skill_ids instead of skills based on the API spec, but the provider rejects that attribute entirely.
Also, the state file gets messy if I try to force it. Just a mess of diffs.
Anyone got a working example of the skills block that actually applies?
The build pipeline is waiting on this.