Could someone explain the specific breaking change introduced in the Genesys Cloud Terraform Provider v1.35.0 regarding the genesyscloud_user resource schema? I am updating my infrastructure-as-code pipeline, which manages user provisioning for a sentiment analysis data ingestion service, and the apply step is failing with a schema validation error that was not present in v1.34.x.
The error indicates that the user_division_id attribute is no longer valid or has been replaced, but the documentation for v1.35.0 is sparse on migration steps for existing state files. I have a minimal reproducible configuration below that worked perfectly in the previous version.
resource "genesyscloud_user" "ml_pipeline_user" {
name = "ML Pipeline Service Account"
email = "[email protected]"
# This field is causing the crash in v1.35.0
user_division_id = var.default_division_id
languages {
language_code = "en-US"
rating = 5
}
roles {
id = var.analyst_role_id
}
}
When I run terraform plan, I receive the following error:
Error: Unsupported argument
on users.tf line 5, in resource "genesyscloud_user" "ml_pipeline_user":
5: user_division_id = var.default_division_id
An argument named "user_division_id" is not expected here. Did you mean to define a block of type "division"?
I suspect the provider now expects a nested division block or a different attribute name like division_id directly, but I want to confirm before migrating my state file to avoid orphaned resources. Is there a recommended pattern for handling division assignment in the new schema, especially when the division ID is derived from a data source lookup? I need to ensure my Python-based user sync script remains compatible with the Terraform state.