2c896ed618
Some checks failed
deploy / fetch (push) Successful in 17s
deploy / deploy-node (bob.hanzalova.internal, 0x134e73f06fa9bdb1dbfa909e149c563f5860ceb71a0e7307918f7033970edf59, benjy.hanzalova.internal, --public-addr /dns4/nh.thgttg.com/tcp/30333) (push) Successful in 30s
deploy / deploy-miner (1, benjy.hanzalova.internal, bob.hanzalova.internal) (push) Successful in 43s
deploy / deploy-metrics (push) Failing after 10s
The dashboard JSON was deployed but its provider config never was, so Grafana had no reason to read the directory -- the dashboard would have been a file on disk and an empty folder in the UI. Tracked separately from the dashboard because Grafana reads providers only at container startup while dashboards are re-read on the provisioning interval: a provider change restarts grafana, a dashboard change does not. validate now queries Grafana's search API for the dashboard uid rather than testing that a file exists, since a provisioned dashboard that fails to parse leaves the JSON looking perfectly fine on disk.