Upgrading our Terraform state to the Genesys Cloud CX as Code provider v1.35.0 just broke our CI pipeline. We’ve been using the genesyscloud_user resource for a while without issues, but after the upgrade, terraform plan starts screaming about a schema change.
The error is specifically about the routing_skills attribute. In the previous version, we passed a list of objects like this:
resource "genesyscloud_user" "agent" {
name = "Test Agent"
email = "test@example.com"
routing_skills {
skill_id = genesyscloud_routing_skill.main.id
level = 5
}
}
Now, the plan output shows:
# module.users.genesyscloud_user.agent will be updated
~ resource "genesyscloud_user" "agent" {
~ routing_skills = [
~ {
~ level = 5 -> null
+ skill_id = "12345678-1234-1234-1234-123456789012"
}
]
}
It looks like the provider is trying to flatten the routing_skills block into a simple list of IDs, or maybe it’s expecting a different structure entirely. The docs for v1.35.0 aren’t super clear on whether level is still supported in that block or if we need to move it to a separate resource.
I tried switching to genesyscloud_user_routing_skill but that feels like overkill for simple updates. Is this a known breaking change where the nested block structure was deprecated? Or am I just missing a new required field? Running terraform refresh doesn’t help since the state file still has the old schema definition.
Any ideas on how to migrate this without deleting and recreating all our users? We have hundreds of agents and recreating them would mess up our historical data and queue assignments.