Connect from libpq service files and match the real Secret layout

The maintainer's login Secrets carry pg_service.conf ([evolution]),
pgpass and ca.crt. Add a strict read_pg_service (known keys only,
verify-full unless a local socket, bounded size) behind --pg-service in
evo-server and evo-world-clone, mount each login Secret whole in the
store Jobs instead of reading aevolution-db, and fix the migrate Job's
PGSERVICE to the [evolution] section. Record the store node choice,
per-environment databases and the backup plan.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-09-29 14:12:26 -04:00
co-authored by Claude Opus 5.5
parent 2d950060db
commit 8d594f28af
12 changed files with 221 additions and 31 deletions
+29
View File
@@ -2728,3 +2728,32 @@ admission policy and the stage and World0 AppProjects, then ran
tool's usage exit. It has not been built locally, because Docker is not running.
- Not executed: anything in the cluster, the store Jobs, retention, rebind and
rotation evidence, and the image build.
## M8.3 service-file connections - 2026-09-29
- The maintainer's dev Secrets have the keys `ca.crt`, `pg_service.conf`
(section `[evolution]`) and `pgpass`, with no `user` key. The values were
pasted into the conversation, so both passwords must be rotated. That rotation
is also the M8.3 credential-rotation evidence step. The values are not recorded
anywhere in the repository.
- `read_pg_service` and `--pg-service` were added to `evo-server` and
`evo-world-clone`.
- Parser tests: a valid file with another section and CRLF lines parses. The
parser refuses:
- `password`, `passfile` and `options` keys;
- `sslmode=require`;
- a repeated key or a repeated section;
- a non-numeric timeout;
- malformed lines;
- a missing section;
- a file over 4 KiB;
- a missing file.
`sslmode=disable` is accepted only for a local socket.
- `check-store --pg-service` against the local cluster verified the probe and the
privilege boundary.
- The store Jobs now mount each login Secret whole (service file, password file,
CA) and no longer read `aevolution-db`. The migrate Job's `PGSERVICE` is now
`evolution`; the previous `evolution-migrator` did not match the maintainer's
file.
- PostgreSQL Release and ASan/UBSan passed. The analysis build passed after one
loop copy was fixed. Deploy policy: 0 failures.