Is there a clean way to define genesyscloud_webrtc_configuration in Terraform to avoid 400 Bad Request during apply? Environment is Genesys Cloud Sydney region. Using Terraform provider version 1.18.0 and GC CLI v2.0.4. The deployment pipeline fails consistently on the WebRTC resource block. Error response indicates missing required field ice_servers or invalid structure for turn_servers. Verified the JSON payload via CLI export from a working manual configuration. The HCL structure matches the provider documentation exactly. State file shows no drift. Previous manual edits were reverted to baseline. The issue persists across multiple environments (dev, staging, prod). Logs show the API rejecting the payload before any server-side processing. Suspect a schema mismatch between the provider definition and the current API endpoint expectations. No other resources in the module fail. Only this specific WebRTC config block triggers the error. Checked for typos in server URLs and credentials. All values are correct and base64 encoded where required. The error message is generic and does not point to a specific line in the HCL file. This blocks the entire deployment pipeline. Need a working example or clarification on the expected schema for this resource in v1.18. Previous versions of the provider accepted similar configurations without issue. The change seems to have introduced stricter validation or a breaking change in the expected format. Any insight into the correct structure for ice_servers and turn_servers within this resource block would be appreciated. Please provide a minimal reproducible example if possible. Thank you.