Sylvain Tremblay
62471e2edf
Consolidating the stack exposed a cycle the individual PRs didn't have: master made harmony_zitadel_auth high-level (config.rs derives harmony_config::Config → depends on harmony_config), while the JWT-bearer branch made harmony_secret depend on harmony_zitadel_auth for the token minter. Result: harmony_secret → harmony_zitadel_auth → harmony_config → harmony_secret. Cargo refuses to build it. The minter (jwt_bearer) is a self-contained, harmony-free leaf used by harmony_secret + harmony-fleet-auth (and re-exported by harmony_zitadel_auth). Move it into a new leaf crate harmony_zitadel_jwt; harmony_zitadel_auth re-exports MachineKeyFile/ZitadelJwtBearer from it so downstream consumers are unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
15 lines
351 B
TOML
15 lines
351 B
TOML
[package]
|
|
name = "harmony_zitadel_jwt"
|
|
edition = "2024"
|
|
version.workspace = true
|
|
readme.workspace = true
|
|
license.workspace = true
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
chrono = { workspace = true }
|
|
jsonwebtoken = "9"
|
|
reqwest = { workspace = true, features = ["json"] }
|
|
serde = { workspace = true, features = ["derive"] }
|
|
serde_json.workspace = true
|