mirror of
https://github.com/Security-Onion-Solutions/securityonion.git
synced 2026-07-22 16:55:40 +02:00
Josh Patterson
da94788255
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.
12 lines
324 B
YAML+Jinja
12 lines
324 B
YAML+Jinja
{% from 'vars/globals.map.jinja' import GLOBALS %}
|
|
{% from 'salt/schedule.map.jinja' import SCHEDULEMERGED %}
|
|
|
|
highstate_schedule:
|
|
schedule.present:
|
|
- function: state.highstate
|
|
- hours: {{ SCHEDULEMERGED.highstate_interval_hours }}
|
|
- maxrunning: 1
|
|
{% if not GLOBALS.is_manager %}
|
|
- splay: 1800
|
|
{% endif %}
|