mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 20:26:33 +00:00
Both roles already mark their only volume backup.disabled (resolver state and redis cache are rebuildable), so the volume-backup drill produced a generation without payload and failed its non-empty assertion. The container_backup consumer is now statically off with the volumes.yml opt-out documenting the exemption, matching the registry roles; derive_includes proves the backup legs leave both closures. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
16 lines
446 B
YAML
16 lines
446 B
YAML
# nocheck: backup-service-flag resolver state is rebuildable cache; the volume is backup-disabled and the consumer permanently off
|
|
---
|
|
data:
|
|
type: volume
|
|
name: unbound_data
|
|
mounts:
|
|
- service: unbound
|
|
target: /etc/unbound
|
|
conf:
|
|
type: config
|
|
source: "{{ [ lookup('container', 'svc-dns-unbound', 'directories.volumes'), 'unbound.conf' ] | path_join }}"
|
|
mode: "0444"
|
|
mounts:
|
|
- service: unbound
|
|
target: /unbound.conf
|