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)
image_ref::ImageRef: parser forfile://,hf://,s3://,ipfs://,oci://URLs.registry::Registrytrait +registry::RegistryError.file::FileRegistry: filesystem-backed registry for tests and air-gapped use. Round-trips a full.pfimg(manifest + every referenced layer blob) into a target directory.hf::HfRegistry,s3::S3Registry,ipfs::IpfsRegistry: trait surface + URL parsing +not_yet_implementedpush/pull gated behind feature flags. Real implementations land in v1.0.1.sign::ManifestSignature/sign::sign_manifest/sign::verify_manifest: cosign-shaped signing for the v1 self-signed mode. Sigstore Fulcio integration is feature-gated (sigstore-keyless) for v1.1.
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
.pfimgartifacts 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
Registrytrait. 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.