Can anyone clarify the validation logic for screen_recording_enabled in genesyscloud_user_settings?
Provider version 1.65.0. Deploying user config with genesyscloud_user_settings. Apply fails with 400 Bad Request. Error: “Invalid field value for screen_recording_enabled”. Boolean expected.
You might want to check at the type coercion behavior in the provider version. The Genesys Cloud API strictly expects a JSON boolean (true or false) for the screen_recording_enabled field, but Terraform often passes string representations if the variable definition is not explicitly typed. This mismatch triggers the 400 Bad Request during the PUT request to the user settings endpoint.
Ensure the variable in your terraform.tfvars or module input is defined as type = bool. If the source data comes from a CSV or external config, it might be read as a string. Casting it explicitly using var.screen_recording_enabled == "true" ? true : false before passing it to the resource can resolve the validation failure. This pattern is common when integrating AppFoundry configurations with infrastructure-as-code tools, where strict schema validation prevents ambiguous data types from reaching the platform API.