Stuck on resolving a schema validation error after upgrading the Genesys Cloud Terraform provider from v1.34.2 to v1.35.0. Our CI/CD pipeline, which manages bulk user provisioning via Python orchestration, is now failing during the terraform plan phase. The error indicates that the genesyscloud_user resource no longer accepts the routing_email_address attribute as a standalone field, suggesting it has been moved or deprecated in favor of a nested routing block or similar restructuring.
Here is the relevant snippet from our module that triggers the failure:
resource "genesyscloud_user" "agent_user" {
name = "${var.first_name} ${var.last_name}"
email = var.email
username = var.email
routing_email_address = var.email # This field is now invalid
division_id = var.division_id
}
The provider logs return a clear attribute mismatch, but the release notes for v1.35.0 are ambiguous regarding backward compatibility for this specific field. I need to understand the new schema structure to update our Python-based Terraform wrapper scripts. What is the correct syntax for defining the routing email address in the updated genesyscloud_user resource schema, and are there any other breaking changes in this version that affect bulk user creation scripts?