In sentry-kubernetes
v6.0.0, config.configYml
was updated to take in YAML instead of the original config format. However, it seems like valid YAML still results in YAML parsing errors within sentry-web
, as follows: in "/etc/sentry/config.yml", line 1, column 1 expected <block end>, but found '-'
.
For context, we’re using Terraform to provision our Sentry deployment. Both of the following YAML values for config.configYml
fail when pushed to prod:
set {
name = "config.configYml"
value = "{slack.client-id: ${var.sentry_config.slack_client_id}, slack.client-secret: ${var.sentry_config.slack_client_secret}, slack.verification-token: ${var.sentry_config.slack_verification_token} , github-app.id: ${var.sentry_config.github_app_id}, github-app.name: ${var.sentry_config.github_app_name}, github-app.webhook-secret: ${var.sentry_config.github_app_webhook_secret}, github-app.private-key: ${replace(var.sentry_config.github_app_private_key, "/\n/", "\\n")}, github-app.client-id: ${var.sentry_config.github_app_client_id}, github-app.client-secret: ${var.sentry_config.github_app_client_secret}}"
}
as well as
set {
name = "config.configYml"
value = <<-EOT
---
slack.client-id: "${var.sentry_config.slack_client_id}"
slack.client-secret: "${var.sentry_config.slack_client_secret}"
slack.verification-token: "${var.sentry_config.slack_verification_token}"
github-app.id: ${var.sentry_config.github_app_id}
github-app.name: "${var.sentry_config.github_app_name}"
github-app.webhook-secret: "${var.sentry_config.github_app_webhook_secret}"
github-app.private-key: "${replace(var.sentry_config.github_app_private_key, "/\n/", "\\n")}"
github-app.client-id: "${var.sentry_config.github_app_client_id}"
github-app.client-secret: "${var.sentry_config.github_app_client_secret}"
EOT
}
Any ideas on what might be going wrong with our YAML, or if there exists some kind of alternative that can still be provisioned via the helm chart values.yaml
?