mirror of
https://github.com/Security-Onion-Solutions/securityonion.git
synced 2026-05-09 12:52:38 +02:00
84197fb33b
The so-postgres-backup script and its cron were living under salt/backup/config_backup.sls, which meant the backup script and cron were deployed independently of whether postgres was enabled/disabled. - Relocate salt/backup/tools/sbin/so-postgres-backup to salt/postgres/tools/sbin/so-postgres-backup so the existing postgres_sbin file.recurse in postgres/config.sls picks it up with everything else — no separate file.managed needed. - Remove postgres_backup_script and so_postgres_backup from salt/backup/config_backup.sls. - Add cron.present for so_postgres_backup to salt/postgres/enabled.sls and the matching cron.absent to salt/postgres/disabled.sls so the cron follows the container's lifecycle.
36 lines
807 B
Plaintext
36 lines
807 B
Plaintext
{% from 'backup/map.jinja' import BACKUP_MERGED %}
|
|
|
|
# Lock permissions on the backup directory
|
|
backupdir:
|
|
file.directory:
|
|
- name: /nsm/backup
|
|
- user: 0
|
|
- group: 0
|
|
- makedirs: True
|
|
- mode: 700
|
|
|
|
config_backup_script:
|
|
file.managed:
|
|
- name: /usr/sbin/so-config-backup
|
|
- user: root
|
|
- group: root
|
|
- mode: 755
|
|
- template: jinja
|
|
- source: salt://backup/tools/sbin/so-config-backup.jinja
|
|
- defaults:
|
|
BACKUPLOCATIONS: {{ BACKUP_MERGED.locations }}
|
|
DESTINATION: {{ BACKUP_MERGED.destination }}
|
|
|
|
# Add config backup
|
|
so_config_backup:
|
|
cron.present:
|
|
- name: /usr/sbin/so-config-backup > /dev/null 2>&1
|
|
- identifier: so_config_backup
|
|
- user: root
|
|
- minute: '1'
|
|
- hour: '0'
|
|
- daymonth: '*'
|
|
- month: '*'
|
|
- dayweek: '*'
|
|
|