Expand description
Config-driven BlobStore selection (ADR-111 Amendment 2).
khive-db cannot parse khive.toml itself (it sits below khive-runtime
in the crate dependency chain), so the fs-vs-s3 selector lives here, one
layer up, where KhiveConfig is already parsed. This is the choke point
every boot path (single- and multi-backend) resolves the configured blob
store through, so the two never drift onto different construction logic.
Functionsยง
- resolve_
blob_ store - Resolve the
BlobStorethisbackendshould use, percfg.storage.blob.