Jean-Gabriel Gill-Couture
af3205d353
`Maestro::initialize` (hence `topology.ensure_ready()`) ran before `init`'s `--list` / confirmation short-circuits, so merely listing a binary's scores — or declining to run them — still prepared the topology (cert-manager install, etc.). Build the maestro unprepared and call `prepare_topology()` only once we commit to interpreting. Expose `Maestro::prepare_topology`; add tests proving `--list` skips prep while the run path triggers it.
28 lines
631 B
TOML
28 lines
631 B
TOML
[package]
|
|
name = "harmony_cli"
|
|
edition = "2024"
|
|
version.workspace = true
|
|
readme.workspace = true
|
|
license.workspace = true
|
|
|
|
[features]
|
|
default = ["tui"]
|
|
tui = ["dep:harmony_tui"]
|
|
|
|
[dependencies]
|
|
assert_cmd = "2.0.17"
|
|
clap = { version = "4.5.35", features = ["derive"] }
|
|
harmony = { path = "../harmony" }
|
|
harmony_tui = { path = "../harmony_tui", optional = true }
|
|
inquire.workspace = true
|
|
tokio.workspace = true
|
|
console = "0.16.0"
|
|
indicatif = "0.18.0"
|
|
lazy_static = "1.5.0"
|
|
tracing.workspace = true
|
|
tracing-subscriber.workspace = true
|
|
|
|
[dev-dependencies]
|
|
harmony = { path = "../harmony", features = ["testing"] }
|
|
async-trait = "0.1"
|