mrhid6 884fd189fb fix: Report the real reason verify falls back to archive-only checks ...

resolveGlobals can fail for two distinct reasons — no MongoDB URI, or no
resolvable database name — and verify.go was printing a hardcoded
no-URI note regardless of which one occurred, misleading an operator
whose URI was fine but whose database name could not be resolved.

2026-09-07 14:11:58 +00:00

..

backup.go

feat: Add the vantagectl backup and inspect subcommands

2026-09-07 13:57:04 +00:00

inspect_test.go

feat: Add the vantagectl backup and inspect subcommands

2026-09-07 13:57:04 +00:00

inspect.go

feat: Add the vantagectl backup and inspect subcommands

2026-09-07 13:57:04 +00:00

restore_test.go

feat: Add the vantagectl restore and verify subcommands

2026-09-07 14:04:25 +00:00

restore.go

feat: Add the vantagectl restore and verify subcommands

2026-09-07 14:04:25 +00:00

root_test.go

feat: Add the vantagectl restore and verify subcommands

2026-09-07 14:04:25 +00:00

root.go

feat: Add the vantagectl restore and verify subcommands

2026-09-07 14:04:25 +00:00

verify.go

fix: Report the real reason verify falls back to archive-only checks

2026-09-07 14:11:58 +00:00