Peter van Arkel 797619acd9 Run post-backup pruning through SQL retention ...

Stop passing prune options into the legacy scheduled backup engine from the
Django backup command. Record the completed snapshot first, then apply retention
through the SQL-backed retention service so pruning sees the same SnapshotRecord
state as the admin and retention command.

Also record prune failures on BackupRun.result instead of leaving the run in an
ambiguous state.

2026-05-19 11:32:32 +02:00

..

__init__.py

feat: make Django configs drive backups and scheduling

2026-05-19 04:53:47 +02:00

test_config_repository.py

refactor: stop using legacy JSON for runtime config

2026-05-19 05:08:37 +02:00

test_configure_commands.py

refactor: replace legacy CLI with Django command surface

2026-05-19 05:14:29 +02:00

test_console_entrypoint.py

feat: discover snapshots into Django records

2026-05-19 05:18:01 +02:00

test_django_config_source.py

refactor: promote backup configuration to structured SQL fields

2026-05-19 05:04:49 +02:00

test_retention_config_source.py

refactor: use injected config sources for retention

2026-05-19 05:00:15 +02:00

test_retention.py

feat: make Django configs drive backups and scheduling

2026-05-19 04:53:47 +02:00

test_run_backup_records_snapshot.py

Run post-backup pruning through SQL retention

2026-05-19 11:32:32 +02:00

test_run_scheduled_config_source.py

refactor: inject config sources into scheduled backups

2026-05-19 04:57:10 +02:00

test_scheduler.py

feat: make Django configs drive backups and scheduling

2026-05-19 04:53:47 +02:00

test_snapshot_discovery.py

Track snapshot base lineage in Django

2026-05-19 11:19:22 +02:00

test_sql_retention.py

Plan Django retention from snapshot records

2026-05-19 11:24:48 +02:00