Skip to main content

Crate pf_registry

Crate pf_registry 

Source
Expand description

§pf-registry

Push / pull .pfimg artifacts to one of five registry backends. See agent_docs/registry-spec.md for the URL-scheme table and the auth conventions.

§What ships in Phase 9 (this commit)

Re-exports§

pub use file::FileRegistry;
pub use hf::HfRegistry;
pub use image_ref::ImageRef;
pub use image_ref::ImageRefError;
pub use ipfs::IpfsRegistry;
pub use oci::OciRegistry;
pub use registry::LayerSet;
pub use registry::Registry;
pub use registry::RegistryError;
pub use s3::S3Registry;
pub use sign::ManifestSignature;
pub use sign::sign_manifest;
pub use sign::verify_manifest;

Modules§

file
Filesystem-backed registry — the build-host test backbone, also useful for air-gapped offline transport (pf push file:///mnt/usb/...).
hf
Hugging Face Hub adapter.
image_ref
URL-scheme parser for ProcessFork registry references.
ipfs
IPFS adapter — uploads .pfimg artifacts into a local Kubo daemon, returns a directory CID that can be served from any IPFS gateway.
oci
Local OCI registry adapter.
registry
The shared Registry trait. Adapter authors implement this; the CLI and SDKs talk to it.
s3
S3-compatible registry adapter (AWS S3 / R2 / MinIO).
sign
Manifest signing. v1 ships the wire format + a self-signed HMAC-SHA256 mode. Sigstore Fulcio (keyless) is feature-gated for v1.1.

Functions§

open
Construct a Registry for a given URL scheme. Returns Err(RegistryError::UnsupportedScheme) for schemes whose implementation lives behind a feature flag we weren’t built with.