You've already forked directdnsonly
Add dry-run mode for reconciliation poller #3
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The first reconciliation pass on a server that has been running without directdnsonly for years will immediately queue deletes for all orphaned zones. There is currently no way to preview what would be deleted before committing.
Proposed solution:
Add a
dry_run: trueoption to the reconciliation config block. When enabled:Config:
This gives operators a way to audit the state of the zone index before enabling live deletion.
Implemented in
app/reconciler.py:dry_runread from config in__init__(defaultfalse)start()logs[DRY-RUN]mode on startup with a prominent warning_reconcile_alllogs[DRY-RUN] Would delete orphan: ...at WARN instead of queuing — backfill/migration writes still apply as they are non-destructiveconfig/__init__.pyapp.ymlcomment block updated withdry_runoptionUsage: set
reconciliation.dry_run: truefor a safe first-run audit pass, then remove or set tofalseto enable live deletion.