Data interchange forjedi
The Juggernaut Electronic Data Interchange (EDI) Rust crate — a data-exchange layer with entity models, JWT/JWKS, RCON, and a shared ClickHouse client.
Shared data-exchange layer
The Juggernaut EDI package, extended through holy and reused across KBVE services for entity modeling, token verification, RCON, and database access. Dry-run: ./kbve.sh -nx jedi:dry --no-cloud.
- Auth — jwks and jwt_cache for JWKS-based JWT verification.
- Telemetry — ClickHouse client batches metrics inserts.
What it gives you
Features
Entity + builder models
entity, builder, and state modules for structured data exchange.
Auth primitives
jwks and jwt_cache modules for JWKS-based JWT verification with caching.
RCON
An rcon module for remote console command exchange.
Proto types
prost / tonic-generated proto module shared across services.
Optional database plumbing
Postgres (tokio-postgres, bb8) and a ClickHouse client behind feature flags, using rustls TLS throughout.
Sanitization
ammonia for HTML/PII cleaning in the exchange path.
Questions
Frequently asked
What is the Jedi crate?
Jedi is the Juggernaut Electronic Data Interchange (EDI) package for KBVE. It provides a robust, scalable data-exchange layer in Rust, with entity models, builders, JWT/JWKS verification, an RCON module, and prost-generated proto types shared across KBVE services.
What does the Jedi crate include?
Its modules include builder, entity, jwks, jwt_cache, proto, rcon, state, and wrapper. It bundles axum, tokio, reqwest with rustls, dashmap, and optional Postgres and ClickHouse plumbing behind feature flags.
Where is the Jedi crate used?
Jedi is a shared KBVE crate reused across services — for example the metrics ingest service uses its ClickHouse client to batch telemetry inserts, and auth paths use its JWKS and JWT cache for token verification.