Skip to main content

Module bundle

Module bundle 

Source
Expand description

Arguments for the decdn bundle subcommand group (issue #391).

Bundles are a publisher-side convenience for grouping multiple BLAKE3-content-addressed blobs into a single JSON manifest file. The manifest itself is also a blob (BLAKE3-hashed), so origins can publish a single bundle hash and clients fetch the bundle then everything it references. See appendix-bundles for the on-disk schema, hash format (b3:<hex>), path-safety rules, and the determinism requirement that makes bundle-as-blob distribution viable.

origin import --dry-run produces manifests; bundle pull (#391) realizes them — fetching every referenced blob over the paid cdn/client/v1 path (decdn fetch’s primitive), with per-entry node discovery and bounded concurrency.

Structs§

BundleArgs
Top-level decdn bundle group.
BundlePullArgs
decdn bundle pull — fetch a bundle’s blobs into a directory.

Enums§

BundleCommand
Subcommands under decdn bundle.