--cron flag help text misstates what it suppresses #87
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?
Last remaining place in the tree that misdescribes
--cron. Split out of#84, which corrected the
Vaultik.UIdoc comment and the README butdeliberately left this one alone: a cobra flag help string is program
output, so changing it is a user-visible change and did not belong in a
docs-only PR.
internal/cli/snapshot.go:138:--cronis not silent unless error.internal/cli/app.go:58-60callsUI.SetQuiet(true), and ininternal/ui/ui.goexactly seven methodscheck
quiet(Beginf,Completef,Infof,Noticef,Detailf,Progressf,Bannerf).Warningf(ui.go:158) andErrorf(
ui.go:167) have no check — warnings are still printed.This is not pedantry:
internal/vaultik/snapshot.go:116-124routes theend-of-run summary through
UI.Warningfspecifically so that crondelivers something. A user who trusts the help text would expect silence
on a successful run and may treat any cron output as a failure signal,
which is backwards.
Definition of done
internal/cli/snapshot.go:138reads"Run in cron mode (silent unless warning or error)", matching theREADME wording corrected in #84.
or log line — still claims
--cronis silent except on error. #84covered the comments and the README; this covers program output.
script/cibuildexits 0, verified as a genuine run rather than acached replay (see #85 — a bare exit code is not evidence until that
lands). State the wall time or show the check layers were not
CACHED.Small enough to fold into another PR touching
internal/cliif one comesalong before this is picked up.