The terraform-provider-genesyscloud is failing to reconcile a data action module during the apply phase. The provider returns Invalid request body (400) when calling /api/v2/integrations/actions/{actionId}/draft/validation. Why would a previously validated schema fail during a terraform apply? It shouldn’t. The workspace is running v1.5.7 of the provider.
GET /api/v2/integrations/actions/{actionId}/draft/validation
The endpoint is a GET. Sending a request body is WRONG and the API is just reacting accordingly. Fix the provider config or stop trying to push data to a read-only call.
PureCloudPlatformClientV2 handles the API requests, but there’s a theoretical possibility that the provider is attempting to send a payload to a GET endpoint because of a version mismatch between the Terraform provider and the platform’s current API state.
Are you using any custom providers or a specific wrapper for the terraform-provider-genesyscloud that might be overriding the standard GET behavior for /api/v2/integrations/actions/{actionId}/draft/validation?
Updating the provider to the latest version did not resolve the issue. The apply phase still fails with Invalid request body (400) during the validation call. Is the provider misconfiguring the HTTP method? It appears so.