Trying to pull the full org config into Terraform for a DR test. Running terraform import on the studio scripts block is bombing out.
Here’s the block I’m using:
resource "nice_cxone_studio_script" "main_flow" {
name = "Main Inbound Flow"
description = "Primary routing logic"
# ... other attrs
}
Command:
terraform import nice_cxone_studio_script.main_flow <script-id-from-api>
Returns:
Error: no matching resource found for "nice_cxone_studio_script.main_flow"
The ID is valid. I copied it straight from the Studio URL. Tried using the API to fetch the script details first via GET /api/v2/analytics/details/flows/{flowId} just to double-check the object structure. The JSON payload comes back fine:
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"name": "Main Inbound Flow",
"version": 12,
"status": "ACTIVE"
}
So the resource exists. The provider seems to be choking on the import logic for Studio objects specifically. I’ve successfully imported users and IVR flows without issue. It’s just the Studio scripts that are throwing this off.
Is there a specific format required for the ID during import? Or is this a known limitation with the current provider version (v2.4.1)? I noticed some GitHub issues mentioning complex objects like scripts and workflows having quirks with state initialization, but nothing concrete on a fix.
We need this for our backup strategy. If the import doesn’t work, the whole DR plan falls apart since we can’t reconstruct the call flows from code.