We are building a disaster recovery workflow using the Genesys Cloud Terraform provider. The goal is to export the entire organization configuration nightly to a remote backend for safekeeping. The issue arises when the source environment has resources that were not created via Terraform. Running terraform export or using the genesyscloud_resource_export data source seems to fail or hang when it encounters these unmanaged resources.
Here is the current configuration block:
resource "genesyscloud_resource_export" "dr_backup" {
export_type = "full"
output_file = "./backup/org-full.json"
}
The process errors out with a state mismatch warning for specific routing profiles that were manually edited in the UI. We need a way to force the export to ignore these drifts or capture the current live state regardless of the Terraform state file. Is there a flag to bypass the state check during the export phase? We’ve tried setting ignore_missing = true but it doesn’t seem to apply to the export resource. Any ideas on how to force a clean snapshot of the live environment?