Genesyscloud_user schema change in v1.35.0 breaking state

General Discussion
1

Quick question about the genesyscloud_user resource in the Genesys Cloud Terraform provider v1.35.0.

Background

Upgraded our CX as Code provider from v1.34.0 to v1.35.0. The release notes mention a schema change for user resources, specifically around division_id handling or implicit defaults.

Issue

Running terraform plan now triggers a force recreate for all existing users. The state file shows the previous schema structure, but the provider expects the new one. This is blocking our nightly CI/CD pipeline.

# module.users.genesyscloud_user.main["dev-01"] must be replaced
-/+ resource "genesyscloud_user" "main" {
 ~ division_id = "default" -> (known after apply)
 # ... other attributes unchanged
}

Troubleshooting

  • Ran terraform state show to verify current state values.
  • Checked provider source code for v1.35.0; no obvious deprecation warnings for division_id.
  • Tried terraform import with no luck as the resource already exists in state.

Is there a recommended migration script or terraform state replace-provider workaround? Or should I pin to v1.34.0 until a hotfix?