Ran into a snag while trying to script our full org export for disaster recovery. The genesyscloud_resource_export data source seems to hang or return partial results when it hits specific queue routing configurations. We’re running the latest provider version (v1.38.0) against a US East org.
The export works fine for users and standard routing rules. It breaks when it tries to pull the genesyscloud_routing_queue resources that have complex wrapping and skill-based routing enabled. The Terraform plan shows the export block, but terraform output returns an empty map for those specific IDs.
Here’s the configuration block we’re using:
data "genesyscloud_resource_export" "dr_snapshot" {
resources = [
"genesyscloud_routing_queue",
"genesyscloud_routing_email_domain",
"genesyscloud_user"
]
filter = {
"routing_queue" = {
"name" = "^Support-.*$"
}
}
}
The debug logs show a 200 OK from the /api/v2/routing/queues endpoint, but the JSON payload returned by the provider lacks the routing_rules array for queues using skill groups. We’ve verified the admin UI shows these rules correctly. Is there a known limitation with exporting nested routing logic in the current provider version, or are we missing a flag to force deep serialization? Checked the release notes but didn’t see anything on this. Ran terraform init -upgrade to ensure no stale plugins.