mirror of
https://github.com/zvx-echo6/central.git
synced 2026-08-26 17:31:39 +00:00
malice
4bbe7d61a6
During the v0.14.0 prod deploy (2026-06-12) migration 042 was applied as `sudo -u postgres`, leaving config.monitoring_areas + its SERIAL sequence owned by postgres while the `central` app role expects ownership-based access. We patched prod inline at the time with ALTER ... OWNER TO central, but the migration FILE was never updated -- so a fresh install (dev clone, eventual prod rebuild) would hit the same footgun. Append two idempotent ALTERs (table + sequence OWNER TO central) so 042 is self-healing. No-op when already central-owned. No new fields/event-types/ behavior, no migration re-apply, nothing to deploy (live prod table is already central-owned via the earlier inline fix). Test: test_grants_table_and_sequence_ownership_to_central asserts both ALTERs are present (whitespace-insensitive, matching the existing static checks). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| migrations | ||
| .gitkeep | ||