Files
computer-playbook/roles/svc-db-postgres/files/shell/dump_pg_hba.sh
kevinveenbirkenbachandClaude Opus 5 575a5a87ac refactor(layout): sort shipped scripts by language and split the unit suite
Every script a role ships now lives under `files/<language>/`, and the unit
suite is split the same way: `tests/unit/python/` beside new sibling trees for
the other languages. `tests/lint/filesystem/test_role_files_layout.py` keeps it
that way; directories whose shape is dictated from outside carry a `.nocheck`
naming the constraint (Docker build contexts, WordPress mu-plugins, the Joomla
extension, Odoo addons, Playwright suites, the `files/test/test.sh` harness
that `test-e2e-cli` resolves generically).

This cannot be applied in halves. Moving a file and repointing what names it
are the same change: 14 references resolve only at deploy time, so the tree is
green either before or after, never between.

Those 14 were found by static resolution over every reference class, not by the
test suite -- a full `make quality-high` was green while all of them were
broken:

  * 7 `src:` values built from a role variable holding a bare filename
    (svc-bkp-remote-2-local, decidim, espocrm, friendica, joomla, pixelfed x2).
    The variable doubles as the destination name inside the container, so the
    language segment belongs at the call site, not in the variable.
  * `sys-service/tasks/04_base.yml` resolved every consumer's systemd script
    through `first_found(..., errors='strict')` over `files/script.{sh,py}`.
    18 roles ship exactly that and have no template fallback: the play would
    have died on each.
  * `sys-front-inj-javascript` fell back to `<role>/files/javascript.js`; the
    interface now reads `files/javascript/javascript.js`.
  * `sys-front-inj-logout/templates/head_sub.j2` built the cache-busting mtime
    path through `path_absolute(... 'files', ...)`.
  * 4 `ansible.builtin.script:` invocations naming a bare command
    (pull.py, prune.sh, set_postgres_superuser_password.sh, ganesha-serve.sh).
  * `dev-python/files/shell/install.sh` pointed at a sibling role's script.

Depth-dependent paths inside the moved trees were bumped accordingly: 59
`parents[N]` computations, 12 relative climbs, and the per-role recover CLI,
whose path `cli/administration/recover/recoverers.py` still assembled from the
pre-move location.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-22 01:31:09 +02:00

44 lines
1.5 KiB
Bash
Executable File

#!/usr/bin/env bash
#
# Postgres-specific rescue diagnostics: capture pg_hba.conf into the shared
# rescue diagnostics folder so it ships in the uploaded snapshot next to the
# generic capture. pg_hba.conf is the auth config the generic rescue script
# cannot capture, which is exactly what a failed TCP-auth wait needs. Prints
# one summary line and always exits 0 so the rescue flow continues to the fail task.
#
# Required environment:
# POSTGRES_CONTAINER_ADDRESS exec address of the postgres container
# PGPASSWORD postgres superuser password
set -u
: "${POSTGRES_CONTAINER_ADDRESS:?POSTGRES_CONTAINER_ADDRESS not set}"
: "${PGPASSWORD:?PGPASSWORD not set}"
export PGPASSWORD
OUT_BASE="${INFINITO_RESCUE_DIAGNOSTICS_DIR:?INFINITO_RESCUE_DIAGNOSTICS_DIR not set (SPOT: group_vars/all/05_paths.yml)}"
mkdir -p "${OUT_BASE}"
out="${OUT_BASE}/postgres-pg_hba.txt"
runtime() {
if command -v container >/dev/null 2>&1; then
container "$@"
else
docker "$@"
fi
}
{
hba="$(runtime exec --env "PGPASSWORD=${PGPASSWORD}" "${POSTGRES_CONTAINER_ADDRESS}" \
psql -U postgres -d postgres -Atc 'SHOW hba_file;' 2>/dev/null || true)"
if [ -n "${hba}" ]; then
echo "hba_file=${hba}"
runtime exec "${POSTGRES_CONTAINER_ADDRESS}" sh -lc \
"sed -n '1,200p' \"${hba}\" 2>/dev/null || true"
else
echo "hba_file could not be determined"
fi
} >"${out}" 2>&1 || true # nocheck: shell-or-true -- grandfathered: worked in practice; TODO: sharpen to catch only the exact tolerated error
echo "🩺 Postgres pg_hba.conf captured to ${out}"
exit 0