Quick question about the genesyscloud_user resource schema changes in the latest CX as Code provider release.
I recently upgraded my Terraform provider from v1.34.2 to v1.35.0 to pick up some bug fixes for Open Messaging integrations, but my existing state files are now blowing up during terraform plan. The provider documentation mentions a “refactor” of the user resource, but it does not explicitly list the breaking changes for the division_id and email attributes. My code was working perfectly fine yesterday.
Here is the specific resource block that is causing the failure:
resource "genesyscloud_user" "om_admin" {
name = "OM Admin Bot"
email = "[email protected]"
division_id = var.om_division_id
username = "[email protected]"
user_type = "AUTO"
}
When I run terraform plan, I get this error:
Error: Unsupported argument
on users.tf line 3, in resource "genesyscloud_user" "om_admin":
3: email = "[email protected]"
An argument named "email" is not expected here.
I have checked the provider v1.35.0 release notes, but they are vague about schema migrations. It seems like the email field might have been removed or moved into a nested block, but I cannot find the new syntax. I am developing this in my Berlin timezone (CET), so I cannot wait for business hours to escalate this.
Has anyone successfully migrated their genesyscloud_user resources to v1.35.0? I need to know the exact replacement for the email argument. I am using Terraform v1.5.7. This is blocking my Open Messaging channel deployment pipeline. I have tried commenting out the email field, but then the API returns a 400 Bad Request saying the user cannot be created without a valid email address. This feels like a provider bug rather than an API change, given that the Genesys Cloud API /api/v2/users still accepts email in the payload. Please advise on the correct HCL structure for this version.