Upgraded our Terraform provider to v1.35.0 this morning and immediately hit a wall with our user provisioning module. The genesyscloud_user resource seems to have dropped the flat address block in favor of a nested structure or renamed attributes, but the changelog is vague.
Here’s the config that worked fine in v1.34.2:
resource "genesyscloud_user" "agent_01" {
email = "agent01@example.com"
name = "Test Agent"
division_id = var.default_division_id
address {
city = "Manila"
state = "Metro Manila"
country = "PH"
}
}
Running terraform plan now throws this:
Error: Unsupported argument
on users.tf line 5, in resource "genesyscloud_user" "agent_01":
5: address {
An argument named "address" is not expected here. Did you mean to define argument "addresses"?
Tried switching to addresses as a list of maps, but the schema validation complains about invalid types. I dug into the provider source code for v1.35.0 and it looks like address is now part of a home_address or similar nested object, but the docs haven’t been updated yet.
Is this a known breaking change? I need to trace these user creations via OpenTelemetry spans, so I can’t just hardcode a workaround without understanding the underlying schema shift. The API call /api/v2/users still accepts the old format, so why is the provider rejecting it?
Looking for a concrete example of the new HCL syntax for v1.35.0. The current state of our infra is frozen because of this.