Has anyone figured out why the genesyscloud_messaging_platform resource fails during plan apply? The environment is us-east-1 with provider version 1.12.4. The configuration looks correct based on the provider documentation, but the API returns a 400 error immediately. No detailed error message in the CLI output, just “Error: 400 Bad Request”.
resource “genesyscloud_messaging_platform” “webchat” {
name = “prod-webchat”
provider_key = “webchat”
provider_secret = var.webchat_secret
enabled = true
}
The secret is stored in AWS Secrets Manager and passed via variable. I have verified the credentials work manually in the Genesys Cloud UI. This blocks our automated deployment pipeline for the Sydney office. Is this a known issue with the current provider version or a schema validation bug?