We’re trying to lock down our queue configurations in Terraform, but the genesyscloud_routing_queue resource keeps choking on the skills definition. We’ve got the provider pinned to 1.42.0 and the syntax looks right based on the docs, yet the plan fails every time.
Here’s the relevant snippet:
resource "genesyscloud_routing_queue" "support_queue" {
name = "Support Queue"
description = "Main support queue"
skills {
skill_id = "some-skill-id-here"
}
}
The error message is pretty vague:
Error: Expected object for "skills" but got list
I’ve tried wrapping the skill_id in a map, using a list of maps, and even hardcoding the skill name instead of ID, but nothing sticks. The API endpoint /api/v2/routing/queues accepts the skill assignments just fine when I curl it directly, so I know the config is valid on the Genesys side. It’s just the Terraform provider that’s throwing a fit.
Has anyone gotten the skills block to play nice? We’re running this against the us-east-1 org. The state file seems clean, no drift detected before the apply attempt. Just straight up schema validation failure from the provider side.
Checked the release notes for 1.42.0 but didn’t see any mention of breaking changes to the queue resource. Might be missing something obvious here. The skill_id is definitely a string, not a reference to another resource in this specific test case. Just a hardcoded UUID for now to rule out dependency issues.
Any pointers on the correct HCL structure for nested skill assignments? The docs example is a bit sparse on the exact nesting level required for the skills array versus a single skill object.