securityonion/salt/salt/defaults.yaml at 66a1141b8410743cd0e2c0927b027a66e4ea6bac - securityonion - CSEC Git

CSEC_PUBLIC/securityonion

mirror of https://github.com/Security-Onion-Solutions/securityonion.git synced 2026-07-19 15:23:41 +02:00

Files

T

Josh Patterson da94788255 Move highstate_interval_hours to salt.schedule and split schedule.sls

highstate_interval_hours describes the per-minion highstate schedule, not the
active-push pipeline, so relocate it from salt.auto_apply to a new salt.schedule
settings subtree. Repoint so-salt-minion-check at the new pillar path (it had
been left on the stale global:push path) so its restart grace period tracks the
schedule again.

- Add salt.schedule.highstate_interval_hours to defaults.yaml/soc_salt.yaml and a
  side-effect-free salt/salt/schedule.map.jinja (SCHEDULEMERGED), matching the
  *MERGED map convention. Consumers read SCHEDULEMERGED.highstate_interval_hours.
- Split salt/schedule.sls into salt/salt/highstate_schedule.sls (every minion) and
  salt/salt/push_drain_schedule.sls (managers); update top.sls to apply the
  highstate schedule via '*' and the drainer schedule via the configured-manager
  block. Remove the now-empty schedule.sls aggregator.
- pillar_push_map.yaml and so-push-drainer: comment/doc updates only.

2026-06-26 10:51:57 -04:00

10 lines

166 B

YAML

Raw Blame History

 salt:
   auto_apply:
     enabled: true
     debounce_seconds: 30
     drain_interval: 15
     batch: '25%'
     batch_wait: 15
   schedule:
     highstate_interval_hours: 2