ObjectStoreViewer scans one configured Barman Cloud or pgBackRest repository root over S3, Azure Blob Storage, or GCS and publishes a bounded, conservative inventory: backups, WAL continuity, timelines, and observed recovery coverage. It turns object-store metadata into something you can read at a glance — completed, running, failed, malformed, missing, or unsupported — without digging through object keys by hand.
Read-only by construction
The application lists, inspects, and reads bounded metadata. There is no upload, delete, restore, or mutation surface anywhere in the codebase — not disabled by configuration, absent by design.
Honest about uncertainty
Incomplete, stale, truncated, or unsupported evidence stays unknown. A partial scan cannot produce a healthy result, and a repository it cannot parse fails visibly rather than quietly.
WAL-aware
Compact WAL ranges, timeline history, duplicates, partial files, and candidate or confirmed gaps — the continuity questions you would otherwise answer by listing object keys by hand.
Cloud-neutral
One evidence model over S3, Azure Blob Storage, and GCS. Provider SDK types stay inside their adapter, and every adapter passes the same shared contract suite.