The last hunk which I applied manually incorrectly retained its pluses.

Fixes: 825a0c92 ("grafana: rebase grafana.ini to grafana 10.2.0-1")

Also add script to make rebasing easier.

Also stop using oauth_auto_login and switch to provider specific
auto_login option.

From [1]: "By default, the new Quarkus distribution removes /auth from
           the context-path."

[1] https://www.keycloak.org/migration/migrating-to-quarkus

Using an inline statement eats the blank line after it; to overcome this
switch to an inline expression, which also happens to be easier to read.

- enable_gzip: grafana listens on localhost, nginx handles compression
- admin_user: initial admin creation is disabled in our config
- strict_transport_security: the same header is set by nginx
- strict_transport_security_max_age_seconds: unused without the above

Symlinking home.json to archive.json causes a duplicate, as both
dashboards have the same uid, and Grafana won't keep the dashboards
updated when there are duplicates[1]. Instead just change
default_home_dashboard_path to point to the archive.json dashboard.

[1] "dashboards provisioning provider has no database write permissions
     because of duplicates"

We don't have any state for dashboards.archlinux.org we want to persist,
so to avoid any stale data in the database, start with a new empty
in-memory database every time Grafana starts.

Grafana v8.2.0 added support for Prometheus's Alertmanager[1] which can
be used with the Unified Alerting added in v8.0.0[2].

[1] https://github.com/grafana/grafana/releases/tag/v8.2.0
[2] https://grafana.com/blog/2021/06/08/grafana-8.0-unified-grafana-and-prometheus-alerts-live-streaming-new-visualizations-and-more/

Mostly changes from Grafana v8.0[1].

[1] https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v8-0/

Thorben Günther authored 3 years ago and Kristian Klausen committed 3 years ago

This reverts commit 649568e7 ("Restrict Grafana access to Arch Linux
Staff group on Keycloak (fixes #151)").