Configuration is broken for some reason when attempting to provision a queue with specific skill requirements using the genesyscloud_queue resource. I am authoring a reusable module for enterprise deployments and need to ensure strict skill adherence. The plan phase succeeds, but apply fails with a 400 Bad Request indicating invalid syntax in the outbound_skill_requirements block.
I have verified the skill IDs exist in the target organization. The structure appears correct based on the provider documentation, yet the API rejects the nested object.
resource "genesyscloud_queue" "sales_queue" {
name = "Sales Support"
description = "Primary sales queue"
outbound_skill_requirements {
required_quantity = 1
skills = [{
id = "${genesyscloud_routing_skill.primary_sales.id}"
quantity = 1
required = true
}]
}
}
Is there a specific formatting requirement for the skills array within the outbound requirements? I suspect the issue lies in how the JSON payload is serialized for the /api/v2/routing/queues endpoint. Please clarify the correct HCL structure for this nested attribute.