Files
securityonion/salt
Mike Reeves 155b5c5d66 fix: consistent allowed_states guard in postgres.schema_pillar
Same `sls.split('.')[0]` pattern as ext_pillar_postgres + pg_notify_pillar_engine.
For sls='postgres.schema_pillar' the split happened to evaluate 'postgres',
which is in manager_states, so the guard worked accidentally — but it would
break silently if anyone ever moved the file under a deeper SLS path. Switch
to a literal `{% if 'postgres' in allowed_states %}` for the same intent-
revealing pattern as the master.d guards.
2026-05-04 19:25:14 -04:00
..
2025-05-30 12:50:59 -04:00
2025-12-02 11:16:08 -06:00
2025-12-11 17:30:06 -05:00
2026-04-24 09:24:58 -05:00
2025-12-02 11:16:08 -06:00
2026-03-23 16:26:56 -04:00
2026-04-09 10:18:36 -04:00
2026-04-24 13:56:35 -04:00
2025-10-30 11:02:36 -04:00
2026-03-06 15:45:36 -05:00
2026-03-19 14:39:10 -04:00
2026-03-19 14:41:49 -04:00
2026-01-07 14:14:57 -05:00
2026-03-23 14:04:48 -05:00
2025-10-14 11:03:00 -04:00
2025-08-04 15:25:26 -04:00