Upgraded to the Genesys Cloud Terraform provider v1.35.0 yesterday and our CI pipeline is now blowing up on the genesyscloud_user resource. The error is Error: Unsupported argument: an argument named "division_id" is not expected here. I’ve been using the standard genesyscloud_user resource for months without issue, passing the division_id to ensure users are provisioned in the correct support queue division. The documentation for v1.34.0 clearly lists division_id as a valid string argument, but the new schema seems to have dropped it or moved it. I’m not seeing a migration guide in the release notes for this specific breaking change. The code snippet that was working fine is just:
resource "genesyscloud_user" "support_agent" {
name = "Tessa Support"
email = "tessa.support@example.com"
division_id = var.support_division_id
phone_types = ["work"]
}
Terraform plan now fails immediately because it thinks division_id is an invalid key. I’ve tried removing the argument to see if it defaults to the user’s home division, but that causes a drift because our existing users are explicitly set to the support division. I need a way to specify the division without triggering a schema validation error. Is this a known regression in v1.35.0 or did I miss a subtle update in the provider docs? The genesyscloud_user resource is pretty critical for our onboarding automation, so I can’t just leave it out. I’ve checked the GitHub issues but haven’t seen anyone else report this specific schema mismatch yet. Maybe I’m blind, but I’m pretty sure this worked last week.