Genesys Cloud Queue Skills Not Persisting in Terraform Apply

General Discussion
1

Why does this setting fail to persist when applying the configuration?

I am building a high-throughput Go service that generates Terraform HCL for our Genesys Cloud infrastructure. We need to provision queues with specific skills assigned. The documentation for the genesyscloud_queue resource suggests using the skills block, but my recent terraform apply results in a diff that never resolves, or the skills are silently dropped after the initial apply.

Here is the relevant HCL snippet generated by my Go template engine:

resource "genesyscloud_queue" "support_queue" {
 name = "Support-Team-Alpha"
 description = "Primary support queue for Alpha region"
 
 skills {
 name = "billing-support"
 level = 5
 }
 
 skills {
 name = "technical-triage"
 level = 3
 }
}

When I run the plan, Terraform shows no changes. When I run apply, it completes successfully. However, checking the Genesys Cloud UI or hitting the /api/v2/queues/{id} endpoint via my Go client reveals that the skills are missing.

Error: Attribute ‘skills’ is not supported or is being ignored by the provider version 1.2.4.

I have verified that the skills billing-support and technical-triage exist in the organization. I am using the latest stable release of the Genesys Cloud Terraform provider. Is the skills block deprecated, or is there a separate resource like genesyscloud_routing_skill that needs to be linked explicitly? I want to avoid writing custom API calls in Go for this mapping if the provider handles it natively. Any insights on the correct schema for skill assignment in queue definitions would be appreciated.

2 
resource "genesyscloud_queue" "support" {
 name = "Support"
 skills = [genesyscloud_skill.general.id]
}

I usually solve this by ensuring the skills list references actual skill IDs from genesyscloud_skill resources. Direct string names fail during reconciliation. Verify the genesyscloud_skill exists before the queue applies to avoid drift.