I’m completely stumped as to why the genesyscloud_edge_cluster resource is failing during the terraform apply phase. The deployment pipeline uses GitHub Actions to push configuration to our BYOC environment in the Sydney region.
The plan phase completes successfully, identifying the new cluster configuration. However, during the apply step, the provider logs show a successful POST to https://api.mypurecloud.com/api/v2/platform/orgs/{orgId}/edge-clusters, but the subsequent polling for the resource status never returns. The process eventually times out with a 504 Gateway Timeout after 300 seconds.
Environment details:
- Terraform v1.7.5
- Genesys Cloud Provider v1.32.0
- OS: Ubuntu 22.04 (GitHub Runner)
- Region: ap-southeast-2
I have verified the API keys have the correct scopes (edge_cluster:write). Manual creation via Postman works instantly. This suggests the issue is specific to how the Terraform provider handles the asynchronous creation workflow or the retry logic for the initial health check.
The debug logs show:
2024-05-20T14:30:00.000Z [DEBUG] Waiting for state to become: [success]
2024-05-20T14:35:00.000Z [ERROR] Request failed after 300s: 504 Gateway Timeout
Is there a known issue with the provider’s wait logic for BYOC clusters? Or is there a specific parameter to adjust the timeout duration?