Just noticed that the Terraform apply is hanging on the BYOC edge resource creation.
Running Terraform v1.8.4 with genesyscloud provider v1.28.0. The pipeline is GitHub Actions, self-hosted runner in Sydney region. The AWS instance is up, health checks pass locally, but the provider fails to register the edge node. The error occurs during the plan refresh phase, not the apply. It seems the CLI or provider cannot verify the edge status before attempting to push the config.
Error log snippet:
Error: Error creating BYOC Edge: Post "https://api.cisco.com/v2/billing/byoc/edges": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
with genesyscloud_byoc_edge.prod-edge-01,
on main.tf line 45, in resource "genesyscloud_byoc_edge" "prod-edge-01":
45: resource "genesyscloud_byoc_edge" "prod-edge-01" {
The edge node is running version 10.3.6.0. I have verified the DNS resolution from the runner to the Genesys endpoints. It resolves correctly. The issue persists across three separate attempts. Is there a known timeout configuration for the provider when dealing with high-latency connections from AU to the US East API region? The standard retry logic in the provider does not seem to catch this specific 503/timeout scenario. I am trying to automate the promotion from DR to Prod and this blocks the entire IaC workflow. Any hints on increasing the HTTP client timeout in the provider block or a workaround?