Is it possible to bypass the 409 Conflict error when creating a genesyscloud_auth_division via Terraform if the division already exists in the Genesys Cloud instance?
We are automating schedule generation and need specific divisions for WFM data isolation. The Terraform provider throws a conflict because the division name matches an existing manual entry. I cannot delete the existing division due to data dependencies.
Here is the configuration causing the failure:
resource "genesyscloud_auth_division" "wfm_division" {
name = "WFM_Automation_Div"
description = "Division for automated WFM schedules"
external_id = "wfm-auto-001"
}
The API returns:
{
"message": "Resource already exists",
"code": 409
}
I have tried using import but the state drift causes issues with subsequent applies. Is there an ignore_changes attribute or a specific API endpoint workaround to force the provider to adopt the existing resource without recreation?