Encountering a persistent validation error during automated environment promotion in the AU (Sydney) region. The pipeline fails when attempting to define custom attribute configurations for Workforce Management via the genesyscloud_wfm_management_settings_custom_attribute resource.
Environment:
- Terraform v1.7.5
- Genesys Cloud Provider v2.15.3
- Region: AU (Sydney)
- Deployment Context: GitHub Actions (DevOps pipeline)
Issue:
The apply step returns a 422 Unprocessable Entity with the following payload:
{
"errors": [
{
"code": "validationError",
"message": "Invalid value for 'is_working'. Must be consistent with attribute type 'NUMBER'."
}
]
}
Terraform Configuration:
resource "genesyscloud_wfm_management_settings_custom_attribute" "attr_shift_score" {
name = "shift_score"
description = "Internal scoring metric"
attribute_type = "NUMBER"
is_working = true # Error triggers here
validation_rules = {
min = 0
max = 100
}
}
Direct API calls using the GC CLI (genesys cloud wfm management settings custom-attributes create) with the same JSON body succeed without issue. This suggests a discrepancy in how the Terraform provider maps the is_working boolean to the API payload structure, specifically for numeric types. The provider documentation implies is_working is optional, but omitting it results in a null value that also triggers a 422, claiming the field is required for new attributes.
Has anyone successfully deployed numeric custom attributes via IaC in the latest provider versions? Is there a workaround to bypass this validation mismatch, or is this a known regression in the genesyscloud_wfm resources? Need a stable solution for the upcoming sprint deployment.