Quick question about Data Action configuration via Terraform.
Using genesyscloud_dataaction resource in provider v1.0.5. Attempting to push a custom data action for outbound campaign enrichment. The HCL config passes terraform plan, but terraform apply fails with HTTP 400 Bad Request.
Error snippet from GC CLI debug output:
POST /api/v2/integrations/dataactions
400 Bad Request
{"errorCode":"bad.request","message":"Validation failed for field 'body'. Expected type 'string', got 'object'."}
The body attribute in HCL is set as a raw string containing valid JSON, matching the structure required by the downstream REST endpoint. However, the Genesys Cloud API seems to be interpreting the input as an object during the schema validation phase.
Environment details:
- OS: macOS Sonoma
14.2 - Terraform:
1.6.4 - Provider:
genesysv1.0.5` - GC CLI:
4.2.1
Is this a known issue with the latest provider version, or is there a specific escape sequence required for the body field to prevent object parsing? The documentation example shows a simple string assignment, which works in the UI but fails in the IaC pipeline. Any workarounds for forcing string type handling?