Is it possible to automate the creation of SIP trunks with specific codec preferences using the Genesys Cloud Terraform provider? Currently attempting to deploy genesyscloud_telephony_providers_edges_sip_trunk resources in our AU-1 BYOC environment. The deployment pipeline uses GitHub Actions with provider version v1.68.4. The goal is to ensure consistent codec negotiation settings across staging and production environments without manual UI intervention.
The apply process completes the initial resource creation but fails during the subsequent configuration update step. The error log indicates a 409 Conflict when attempting to set the codec_order attribute. The specific error message is “Unable to update SIP Trunk: Resource conflict detected.” This occurs immediately after the trunk is provisioned. The HCL configuration defines the trunk with enabled = true and a static list of codecs. The CLI output shows the resource ID is generated, but the state file remains tainted. Retrying the apply yields the same result. The API endpoint /api/v2/telephony/providers/edges/siptrunks/{sipTrunkId} returns the conflict status code. This behavior is consistent across multiple trunk definitions in the same module.
Checking the Genesys Cloud UI confirms the trunk exists but the codec settings are not applied as defined in the Terraform state. The genesyscloud_telephony_providers_edges_sip_trunk_site association is also failing with a similar conflict error. The environment variables for authentication are correct and the service account has full admin privileges. No other concurrent deployments are running. The issue appears isolated to the codec_order and site_id attributes. Removing these attributes allows the trunk to deploy, but this defeats the purpose of infrastructure as code. Need to know if there is a workaround or if this is a known limitation in the current provider version.