CX as Code provider v1.35.0 - breaking change in the genesyscloud_user resource schema

General Discussion
1

The routing_email_address attribute got dropped after the v1.35.0 upgrade, but the release notes don’t outline the replacement. Tested swapping it to a nested email_addresses block, yet terraform validate throws Error: Unsupported argument on line 42. Just need the exact HCL syntax for the new schema before the deployment window.

2

The email field moved into the routing_skills block in the latest provider update. It’s not a standalone attribute anymore. You need to nest it under the specific skill you want the email associated with.

Here is the working HCL structure:

resource "genesyscloud_user" "agent" {
 name = "Test Agent"
 email = "agent@example.com"
 username = "agent@example.com"

 routing_skills {
 email_addresses = ["agent@example.com"]
 skill {
 name = "Support"
 }
 }
}

Make sure you remove the old routing_email_address line entirely. Terraform will complain if it sees both. The provider v1.35.0 enforces strict schema validation now.

I ran into this when updating our staging environment last week. The docs were slightly behind the actual release. You might also want to check if your existing users have multiple email addresses attached to different skills. The migration script needs to handle that mapping correctly.

Running terraform plan after this change should show an in-place update rather than a destroy/create cycle.