Use explicit PostgreSQL superuser name and fix check mode #17

Merged
eblume merged 1 commit from feature/postgresql-explicit-superuser into main 2026-01-16 14:41:36 -08:00
Owner

Summary

  • Add postgresql_superuser variable (eblume) to prevent PostgreSQL from inheriting OS username during initdb
  • Update all psql/createdb commands to use explicit -U flag
  • Add check_mode: false to op commands so 1Password fetches run during --check mode
  • Add PostgreSQL and Miniflux health checks to indri-services-check

Test plan

  • Renamed existing superuser from erichblume to eblume
  • Ran mise run provision-indri -- --tags postgresql --check --diff successfully
  • Verified connection as eblume superuser via Tailscale
  • Ran mise run indri-services-check - all services healthy

🤖 Generated with Claude Code

## Summary - Add `postgresql_superuser` variable (`eblume`) to prevent PostgreSQL from inheriting OS username during initdb - Update all psql/createdb commands to use explicit `-U` flag - Add `check_mode: false` to op commands so 1Password fetches run during `--check` mode - Add PostgreSQL and Miniflux health checks to indri-services-check ## Test plan - [x] Renamed existing superuser from `erichblume` to `eblume` - [x] Ran `mise run provision-indri -- --tags postgresql --check --diff` successfully - [x] Verified connection as `eblume` superuser via Tailscale - [x] Ran `mise run indri-services-check` - all services healthy 🤖 Generated with [Claude Code](https://claude.com/claude-code)
- Add postgresql_superuser variable (eblume) to prevent inheriting OS username
- Update initdb to use -U flag for explicit superuser creation
- Update all psql/createdb commands to use explicit -U flag
- Add check_mode: false to op commands so 1Password fetches run in --check mode
- Add PostgreSQL and Miniflux to indri-services-check

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
eblume merged commit 812b78bf61 into main 2026-01-16 14:41:36 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!17
No description provided.