Terraform genesyscloud_user schema break in v1.35.0

General Discussion
1

No idea why this is happening, our Terraform plan fails after upgrading the Genesys Cloud provider to v1.35.0. The genesyscloud_user resource schema appears to have changed unexpectedly. The documentation states: “The user resource schema remains stable across minor versions.” Yet, I am seeing this error:

Error: Unsupported argument

 on main.tf line 12, in resource "genesyscloud_user" "test":
 12: username = var.user_name

An argument named "username" is not expected here.

Why is this happening?

1 Like
2

It depends, but generally…

  • Check the changelog for genesyscloud_user in v1.35.0; username was likely replaced by email as the primary identifier.
  • Update your HCL to use email = var.user_email and remove the username block to resolve the schema error.
3 Likes
3

Yep, this is a known issue with the v1.35.0 schema update. email is now the required identifier, so you must drop username and map your variable to the new field to pass validation.

resource "genesyscloud_user" "test" {
 email = var.user_email
}
4

It depends, but generally… the schema change is real. I hit this too.

resource "genesyscloud_user" "test" {
 email = var.user_email
}

Dropping username fixes the plan. My Deno webhooks rely on email for user lookup now anyway, so this aligns well. Just verify your existing users have valid emails.

1 Like
5

If I remember correctly… docs state “email is the primary identifier.” i am confused why username was removed. it breaks my simple flows.

you must use email. the suggestion above shows this. i copy-pasted it and it worked. do not use username.

docs say “schema changes require migration.” i get errors if i ignore this. just update the hcl file.