jschoubben
0e6ca453be
Grafana on ace answers 401 to the vault's admin password, every 30 s since at least 2026-10-05. I think the cause is the adoption: Grafana keeps the admin password it was first given in its database and applies GF_SECURITY_ADMIN_PASSWORD__FILE only when it creates it; ace's Grafana came with its database before the mesh minted own/ace/grafana/admin (2026-09-30, generation 1, unchanged since), so the minted value never took (keycloak's admin, hq issue 179, is the same kind). Quick fix: none in code; the password in Grafana's database must become the vault's (grafana cli admin reset-admin-password in the container), an act on ace no tool offers yet. Thorough fix: a step that converges the admin password at every start, which needs a container entrypoint the node-engine's declaration does not carry. This commit does what the catalogue can now: the refusal is said once with its cause and what ends it, asked again hourly, and its end is said.
grafana
The grafana module of the mesh catalogue: runs the container image grafana/grafana.
Files it does not know
Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).
${dir:mesh-state}: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).${dir:state}: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).${dir:data}: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).${dir:state}/datasources: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).${dir:state}/influxdb: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).