Running into a wall trying to import an existing Genesys Cloud Web Messaging configuration into our Terraform state. We’ve been managing this manually via the UI for a while, but I want to move it into code.
I’m using the genesyscloud provider v1.65.0. The resource type is genesyscloud_webmessaging_config. I grabbed the ID from the URL in the Genesys admin portal, which is 4f9a2b1c-8d7e-4f6a-9b0c-1d2e3f4a5b6c.
Ran the import command:
terraform import genesyscloud_webmessaging_config.main 4f9a2b1c-8d7e-4f6a-9b0c-1d2e3f4a5b6c
The command completes without error, but when I run terraform plan, it shows a massive diff. It wants to delete the existing config and create a new one. The issue seems to be with the brand_id field. The API returns the brand ID, but Terraform doesn’t seem to be reading it correctly during the import refresh.
Here’s the relevant snippet from my .tf file:
resource "genesyscloud_webmessaging_config" "main" {
name = "Production Web Messaging"
brand_id = "12345678-abcd-efgh-ijkl-1234567890ab" # This is the actual brand ID
# ... other settings ...
}
The debug logs show the API call to GET /api/v2/webmessaging/configs/{id} returns a 200 OK with the correct JSON payload including the brandId. But the state file ends up with brand_id = null.
Is there a known issue with importing this specific resource? Or am I missing a step in the import process for resources that depend on brand context? I’ve checked the provider docs and they don’t mention any special import arguments for this resource type.