Why does this setting fail validation on Genesyscloud_ivr_script via Terraform?

Architect & Flows
1

Why does this setting return 400 when pushing a simple IVR script update via Terraform? The flow works fine in the Architect UI, but the API rejects the payload during terraform apply.

env: us-1 prod
provider: genesys 1.15.4
tf: 1.6.5
resource: genesyscloud_ivr_script

The specific error occurs at the POST /api/v2/flow/ivrs/scripts endpoint. The response body indicates a validation failure on the language_pack reference.

Error: Error updating IVR script "main-menu-v2": 400 Bad Request
{
 "errors": [
 {
 "code": "invalid_argument",
 "message": "Language pack ID 'en-US' does not exist or is not accessible."
 }
 ]
}

The HCL configuration uses the standard ID returned by genesyscloud_language_pack data source.

data "genesyscloud_language_pack" "en_us" {
 id = "en-US"
}

resource "genesyscloud_ivr_script" "main_menu" {
 name = "Main Menu v2"
 language_pack = data.genesyscloud_language_pack.en_us.id
 
 prompt {
 name = "welcome_msg"
 text = "Welcome to our support line."
 }
}

Debugging the plan shows the ID is correctly resolved to en-US. Manual API calls using the same ID in Postman work without issues. The Terraform provider seems to be stripping or misformatting the ID during the request generation phase. Log traces show the payload sends language_pack: null despite the HCL definition.

  • Verified the language pack ID exists and is active in the organization via the Admin UI and direct API GET calls.
  • Tested with a hard-coded string "en-US" instead of the data source reference, resulting in the same 400 error with null value in the logs.

Is this a known bug in provider version 1.15.4? Or is there a specific attribute required for the script resource to correctly bind the language pack during creation?