From 86dfc9ee251b07ad914ef26646af0079b7a5cadb Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Thu, 21 Dec 2023 09:22:08 +1100 Subject: [PATCH] graphite: add grafana header to CORS allowed list Honestly we're not 100% sure where this CORS setup came from, it's always been like this. grafana recently added a header it's sending to graphite [1] (found by frickler) which we need to white-list so it works with modern grafana. [1] https://github.com/grafana/grafana/commit/1a281ac49dd6b9ee6964badb832918507bf8ba97#diff-70030faa245250908d55db47258ce505d474db1559995683f8df1a951504236fR24 Change-Id: I21570bd1a350e430bc04a14ad9d2cb1bf652d021 --- playbooks/roles/graphite/templates/graphite-statsd.conf.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/playbooks/roles/graphite/templates/graphite-statsd.conf.j2 b/playbooks/roles/graphite/templates/graphite-statsd.conf.j2 index d68c4c38bf..a440e27241 100644 --- a/playbooks/roles/graphite/templates/graphite-statsd.conf.j2 +++ b/playbooks/roles/graphite/templates/graphite-statsd.conf.j2 @@ -54,7 +54,7 @@ server { add_header 'Access-Control-Allow-Origin' '*'; add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS'; - add_header 'Access-Control-Allow-Headers' 'Authorization, Content-Type'; + add_header 'Access-Control-Allow-Headers' 'Authorization, Content-Type, X-Grafana-Device-Id'; add_header 'Access-Control-Allow-Credentials' 'true'; }