Genesyscloud_user schema breaking change in cx-as-code v1.35.0

General Discussion
1

can anyone clarify the breaking change in the genesyscloud_user resource schema for cx-as-code provider v1.35.0?

error: unsupported argument "routing_email", have to use "routing_profile_id" instead

my terraform plan fails immediately on existing resources. did the api change or is this a provider bug?

2 Likes
2

According to the docs, they say the routing_email argument was deprecated in favor of explicit profile binding. This is not a bug. It is a schema enforcement update.

  1. Locate your genesyscloud_user resource blocks.
  2. Remove the routing_email argument entirely.
  3. Add routing_profile_id and set it to the output of your genesyscloud_routing_profile resource.

If you are managing this via a GraphQL gateway, ensure your DataLoader batch fetches the profile ID before the user mutation. The REST API /api/v2/users/{id} now requires the profile ID in the request body for routing updates.

resource "genesyscloud_user" "agent" {
 name = "Test Agent"
 email = "[email protected]"
 routing_profile_id = genesyscloud_routing_profile.default.id
}

Running terraform plan after this change will show no diffs for existing resources if the ID matches. Stop trying to pass email strings for routing logic. It breaks the schema contract.