Module manifest 

What a capture writes beside its artifacts, and the check that reads it back.

A capture is a directory of opaque bytes: an operator cannot look at a controller checkpoint and tell whether it arrived whole. The manifest is what makes the copy checkable — it names every artifact with the size and the SHA-256 of the bytes that were uploaded, so krabka-backup verify can answer the only question that matters before a disaster, which is whether this copy would restore.

Structs

Artifact

One captured artifact, as it was uploaded.

Manifest

The record of one capture.

Constants

CAPTURE_ROOT

Directory the captures live under, inside the archive.

DISKLESS_WAL_INDEX

Object name of the committed diskless-WAL projection.

GROUP_OFFSETS

Object name of the captured committed group offsets.

MANIFEST

Object name of the manifest inside one capture.

MANIFEST_VERSION

Version of manifest.json, its required top-level "version" field.

METADATA_CHECKPOINT

Object name of the captured controller metadata checkpoint.

RLMM_SNAPSHOT

Object name of the captured RLMM snapshot.

Functions

artifact_problem

What is wrong with one artifact’s bytes, or None when they are the bytes the manifest recorded.

sha256_hex

Lowercase hex SHA-256 of bytes.