Mike Reeves 011749ad09 Self-heal PostgreSQL SOC database bootstrap ...

init-db.sh only runs on a fresh PGDATA (docker-entrypoint-initdb.d), so a
cluster left partially initialized -- e.g. the container restarted mid first-init
by a watch trigger -- never recovered: the so_postgres role existed but its
schema grants and the so_telegraf database were missing, breaking SOC with
"permission denied for schema public".

- init-db.sh: make the role upsert race-safe. Try CREATE ROLE and fall back to
  ALTER on duplicate_object/unique_violation instead of IF NOT EXISTS, so a
  concurrent creator no longer aborts the script (set -e + ON_ERROR_STOP=1)
  before the grants and so_telegraf creation run. The whole script is now
  idempotent and safe to re-run.
- postgres/enabled.sls: move postgres_wait_ready here (was telegraf-gated in
  telegraf_users.sls) and add postgres_bootstrap_soc_db, which re-runs init-db.sh
  every highstate so a partially-initialized cluster self-heals.
- telegraf_users.sls: drop its now-duplicate postgres_wait_ready definition; it
  resolves from postgres.enabled via the existing include.
- soup: remove bootstrap_so_soc_database and its post_to_3.2.0 call. The
  highstates soup runs before postupgrade now reconcile the SOC DB, making the
  one-shot bootstrap redundant.

2026-07-20 15:04:58 -04:00

..

init-db.sh

Self-heal PostgreSQL SOC database bootstrap

2026-07-20 15:04:58 -04:00

pg_hba.conf

Use TELEGRAFMERGED for telegraf.output and de-jinja pg_hba.conf

2026-04-20 16:06:01 -04:00

postgresql.conf.jinja

Harden postgres secrets, TLS enforcement, and admin tooling

2026-04-20 12:36:17 -04:00