Is it possible to force immediate registration validation after creating a SIP trunk via the Terraform provider?
We are automating telephony edge deployments using the Genesys Cloud Terraform provider version 1.48.2. The environment is AP-SYDNEY-1. Terraform version is 1.7.5.
The deployment pipeline uses GitHub Actions. The job creates the genesyscloud_telephony_providers_edges_site and the genesyscloud_telephony_providers_edges_trunk resource. The HCL configuration is standard. Static IP is assigned. Port 5060 is open. Firewall rules are verified.
terraform apply completes successfully. The resources are created in the platform. However, the trunk status remains “Unregistered” for approximately 15 to 20 minutes. This delay breaks our CI/CD validation step. The test call fails because the trunk is not ready.
We cannot wait for manual intervention. We need the trunk to be active immediately after the apply command finishes.
I have checked the Genesys Cloud API documentation. The POST /api/v2/telephony/providers/edges/trunks endpoint returns a 201 Created status. The response body contains the trunk ID and configuration. It does not contain a registration status field that indicates readiness.
I tried adding a depends_on block to a subsequent resource that attempts a test call. It fails with a 400 Bad Request. The error message is “Trunk is not registered or active.”
Is there a hidden API endpoint to trigger registration?
Or is there a way to configure the trunk resource in Terraform to retry registration immediately?
We are considering writing a custom null_resource with a local-exec script to poll the API. This feels like a workaround. It should be handled by the provider.
The provider documentation for genesyscloud_telephony_providers_edges_trunk does not mention any timeout or retry parameters. It only lists standard fields like name, description, and auth method.
Any insights on how to handle this synchronization issue in an automated pipeline would be appreciated. We are stuck on this deployment step.