Has anyone else hit the wall with the new v1.35.0 Terraform provider where the genesyscloud_user resource completely changed its schema? I was managing our agent roster with a pretty standard setup using the routing_email and routing_phone_number blocks directly under the user resource. After updating the provider, the plan starts screaming that these attributes are no longer valid and I need to move them into a separate genesyscloud_user_routing_profile association. It feels like a major breaking change for a patch version update. My current config looks like this:
resource "genesyscloud_user" "agent" {
name = "Test Agent"
routing_email {
address = "agent@test.com"
}
}
I’ve tried commenting out the routing blocks to see if it applies the user first, then adding the routing profile separately, but the dependency chain gets messy. The documentation isn’t super clear on the migration path for existing state files. Is there a specific way to refactor this without wiping the user state? I don’t want to lose the historical data associated with the user ID in Genesys Cloud. The error message just says “An attribute named “routing_email” is not expected here” which is helpful but doesn’t tell me what to do next. I’ve checked the release notes but they are vague about the removal of inline routing configuration. How are you all handling this transition for large user bases? It seems like the provider team shifted the responsibility to a separate resource type but didn’t provide a smooth upgrade path. I’m stuck on this for now.