Hey everyone, ran into a weird one with the cx-as-code pipeline. The genesyscloud_terraform_provider is failing to reconcile a specific data action config during a terraform apply. Every time the pipeline runs, it detects a diff on the integration_action resource and tries to fire a PATCH /api/v2/integrations/actions/{actionId} to fix it, but the apply just hangs or returns a generic 500.
genesyscloud-terraform-provider handles the resource mapping for these actions, but the terraform.tfstate keeps showing a mismatch on the configuration block. It’s driving me nuts because the raw JSON in the provider looks identical to what’s in the UI.
Tried to manually force the state with terraform import to see if that would stop the loop. The logs show the provider is hitting the PATCH endpoint with a payload that should be a no-op, but the API isn’t accepting it.
resource "genesyscloud_integration_action" "my_action" {
name = "GetCustomerData"
integration_id = "12345-abcde-67890"
configuration = {
request = {
requestUrl = "https://api.example.com/data"
requestMethod = "GET"
}
response = {
responseTimeout = 5000
}
}
}
The terraform plan output shows the configuration attribute shifting between null and a populated object on every single run. For what it’s worth, the actionId is definitely correct and the credentials have full admin scopes. Not sure why the provider can’t stabilize the state for this specific resource.