Genesyscloud_user schema broke in v1.35.0 terraform provider

General Discussion
1

Upgraded the genesyscloud vider to v1.35.0 this morning and now my genesyscloud_user resources are failing validation. The docs still show the old schema but the plan output is screaming about missing attributes.

Here’s the error I’m getting:

Error: Missing required argument

 on users.tf line 45, in resource "genesyscloud_user" "agent_01":
 45: resource "genesyscloud_user" "agent_01" {

The argument "routing_email_address" is required, but no definition was found.

Wait, that’s not it. Let me check the logs again. Actually it’s complaining about routing_email_address being deprecated and removed, but now it wants routing_email? No, it’s just failing on the email attribute entirely.

Here is the resource block:

resource "genesyscloud_user" "agent_01" {
 name = "Test Agent"
 email = "test.agent@example.com"
 division_id = var.default_division_id
 
 username = "test.agent"
 
 roles {
 id = var.agent_role_id
 }
}

Plan fails with:

Error: Unsupported argument

 on users.tf line 52, in resource "genesyscloud_user" "agent_01":
 52: email = "test.agent@example.com"

An argument named "email" is not expected here.

So email is gone? Replaced by what? The changelog for 1.35.0 just says “Updates to user schema” which is incredibly vague.

Tried these steps:

  • Downgraded to v1.34.0. Plan works fine.
  • Upgraded to v1.35.0. Plan fails.
  • Checked the vider source code on GitHub. The email field seems to be moved or renamed but the docs haven’t caught up.
  • Tried adding routing_email_address explicitly. Still fails.

Is anyone else hitting this? I have 200+ users defined and I can’t just rewrite them all without knowing the correct attribute name. The API endpoint /api/v2/users/{id} still accepts email, so this feels like a vider bug rather than an API change.

Running terraform 1.6.5 on macOS.