Files
harmony/examples/fleet_server_install/Cargo.toml
Sylvain Tremblay 978f3050f7 feat(fleet): use harmony_cli for example output + nicer Score outcomes
Switch example_fleet_server_install from a manual `create_interpret().
execute()` + `println!` to `harmony_cli::run`, which wires up the
framework's standard logger + reporter — emoji-tagged per-Score
progress lines and an end-of-run summary listing each Score's
`Outcome.details`. Mirrors the okd_add_node example's pattern.

For events to fire on the inner Scores, FleetServerScore now calls
`Score::interpret` (not `create_interpret().execute`) on
NatsBasicScore + FleetOperatorScore. Same change inside
FleetOperatorScore for its inner HelmChartScore.

Outcome.details populated:
- FleetOperatorScore: image, namespace, release_name, NATS URL.
- FleetServerScore: in-cluster NATS URL, kubectl pointer to the
  operator deployment, kubectl tip for verifying CRDs.

Progress logs added inside FleetOperatorScore between the chart-
render and helm-install phases (`info!`).

FleetOperatorScore fields are now `pub` so callers can read them
post-construction (FleetServerScore needs `operator.namespace` for
its summary). Builder methods unchanged; both styles coexist.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-04 18:31:23 -04:00

17 lines
368 B
TOML

[package]
name = "example_fleet_server_install"
version.workspace = true
edition = "2024"
license.workspace = true
[[bin]]
name = "fleet_server_install"
path = "src/main.rs"
[dependencies]
harmony = { path = "../../harmony", default-features = false }
harmony_cli = { path = "../../harmony_cli" }
tokio.workspace = true
anyhow.workspace = true
clap.workspace = true