So I’m seeing a very odd bug with genesyscloud_webrtc resource updates in our AU-1 BYOC environment. The Terraform plan shows no changes, but the apply step fails with a 409 Conflict error. This happens specifically when trying to update the default_codec setting via CLI v2.1.0.
The pipeline uses GitHub Actions to push configuration from dev to prod. The dev environment applies cleanly. Prod rejects the payload.
Error log from the CLI output:
Error: Conflict updating WebRTC configuration
Status: 409
Message: The resource is currently being modified by another process or has conflicting settings.
Resource ID: webrtc-softphone-config-001
I checked the API directly using the endpoint PUT /api/v2/users/me/web-rtc. The response body indicates a conflict with the ice_server configuration, even though our HCL does not modify ICE servers. It seems like the platform is locking the resource because of an internal async process, possibly related to STUN server validation in the AU-1 region.
Here is the relevant HCL snippet:
resource "genesyscloud_webrtc" "default" {
enabled = true
default_codec = "opus"
# ice_server is commented out, using defaults
}
We are using the genesyscloud provider version 1.42.0. The default_codec change is minor, but the 409 suggests a deeper state mismatch. Is there a known issue with WebRTC resource locking in AU-1 BYOC? Or is there a specific API call needed to unlock the resource before the CLI push?
Reference: Genesys WebRTC API Docs
Timezone: Sydney. Environment: AU-1 BYOC. Terraform: 1.6.0.