nordisk/holger

holger-agent-cli — crate card

Reverse-engineered (from source — verify, don't trust the name)

• One-line pitch: The holger-agent binary — a source→target artifact transfer tool for airgap movement.
• Does: clap ValueEnum-driven CLI over holger-agent-lib. Source = World (crates.io, needs lockfile) / Nexus / Artifactory / Holger / Znippy / TarZstd / Directory; Target = Znippy / TarZstd / Directory / Nexus / Artifactory / Holger, with an AuthMode selector. Reads from any source connector, packs/pushes to any target — the internet-side half of the airgap workflow.
• Key deps: agent-lib, traits, clap (derive+env), tokio, env_logger. Dev-deps stand up real integration tests: mannequin (mock Nexus/OIDC/PKI), the rust/maven/python repository backends, testcontainers, and the nexus/artifactory comparison benchers.
• Shape: bin (holger-agent), single main.rs.
• Observed role in the workspace: The operator-facing airgap transfer entrypoint; the counterpart to holger that runs internet-side.

Fill in (one line each — only the human knows these)

• Primary consumer(s):
• Why it exists (vs the obvious alternative):
• Hard constraint (airgap / no-C-deps / no-FFI / pure-Rust / etc.):
• Release cadence & independence (rides a parent? own repo someday?):
• Status (production / prototype / experimental / stubbed):
• Must-NOT-change invariant:
• Biggest known gap or TODO:
• Anything a newcomer would get wrong about it: