What’s the best way to handle the breaking change in the genesyscloud_user resource schema for CX as Code provider v1.35.0? My Jupyter notebook automation uses the Python SDK to drive Terraform state updates. The new schema requires explicit user_divisions mapping, causing plan failures on existing users.
resource "genesyscloud_user" "agent" {
name = "Test Agent"
# user_divisions is now mandatory but undocumented in migration guide
}
I need the exact JSON payload structure for the user_divisions attribute to suppress the validation error. Standard string interpolation fails.