From 039ed9c66a50bce6a9486d4b94dd9c1b72b6dc32 Mon Sep 17 00:00:00 2001 From: sneak Date: Mon, 21 Sep 2026 07:23:02 +0000 Subject: [PATCH] Correct --cron flag help to name warnings as unsuppressed (closes #87) The --cron help string claimed "silent unless error", but cron mode sets UI.SetQuiet(true), which suppresses only the seven quiet-aware UI methods; Warningf and Errorf still print. The snapshot terminus deliberately routes its end-of-run summary through Warningf so cron delivers something on success, so a user trusting the old text could read normal output as a failure signal. The string now reads "silent unless warning or error", matching the README wording corrected in #84. No behavior change. Model: opus-4-8 --- internal/cli/snapshot.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/cli/snapshot.go b/internal/cli/snapshot.go index 9d94daa..7460169 100644 --- a/internal/cli/snapshot.go +++ b/internal/cli/snapshot.go @@ -135,7 +135,7 @@ specifying a path using --config or by setting VAULTIK_CONFIG to a path.`, } cmd.Flags().BoolVar(&opts.Cron, "cron", false, - "Run in cron mode (silent unless error)") + "Run in cron mode (silent unless warning or error)") cmd.Flags().BoolVar(&opts.Prune, "prune", false, "After backup, drop older snapshots of the same name and remove "+ "orphaned blobs")