holger-mannequin — crate card
Reverse-engineered (from source — verify, don't trust the name)
- One-line pitch: A test-dummy daemon that mocks the entire external world — PKI, OIDC, Nexus, and auth — for holger dev and integration tests.
- Does: Bundles four mock services (modules
pki— CA mgmt/cert issuance/regen;oidc— /token, /userinfo, discovery;nexus— proxy + upload mock;auth— users/roles/validate/issue) behind an axumMannequinServer, plus anEventLogand an optional eguiMannequinGui(--gui, drawn with facett SystemChart + Table) showing a live system map and per-node request logs. Runs in-process (integration tests, no network) or standalone (mannequin serve). Also impersonates Nexus for the holger-vs-Nexus benchmark so both run against the same mock backend. - Key deps:
axum,tokio,cert-helper(PKI),reqwest(rustls),clap,uuid,base64,chrono,ron,tempfile; GUI:eframe/egui+facett-core/facett-syschart/facett-table. - Shape: both — lib (
mannequin) +holger-mannequinbin. ~8 modules incl. auth/, nexus/, oidc/, pki/ subdirs. - Observed role in the workspace: Dev/test-only. Used by agent-cli integration tests and the bench comparison; replaces Keycloak + Nexus + a CA in one process.
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: