Noop change to retrigger lists3 deployment

We've been trying to get this to deploy automatically without much
success due to a couple of unrelated errors. The most recent appears to
possibly be an ansible issue within ansible itself (eg not our
playbooks). Land a noop change to retrigger things and see if this is
consistent or not.

Change-Id: Iaf0aa14a82fb7d0a2b61a5138c7435d3eda21a3e
This commit is contained in:
Clark Boylan 2023-10-16 11:54:48 -07:00
parent 944b78154d
commit 53fe07271c

View File

@ -1,3 +1,4 @@
# System Configs
iptables_extra_public_tcp_ports: iptables_extra_public_tcp_ports:
- 25 - 25
- 80 - 80
@ -20,6 +21,7 @@ borg_backup_excludes_extra:
- /var/backups/mailman-mariadb - /var/backups/mailman-mariadb
# Can regenerate indexes from source email files # Can regenerate indexes from source email files
- /var/lib/mailman/web-data/fulltext_index - /var/lib/mailman/web-data/fulltext_index
# Exim Configs
exim_queue_interval: '1m' exim_queue_interval: '1m'
exim_queue_run_max: '50' exim_queue_run_max: '50'
exim_smtp_accept_max: '100' exim_smtp_accept_max: '100'