Jean-Gabriel Gill-Couture
eea006535b
Scores own deploy. harmony_app is identity, images, context, and HarmonyApp→Scores. Authoring DX lives in dx. Compose/chart/Application model and the Helm render test are gone.
28 lines
829 B
Markdown
28 lines
829 B
Markdown
# harmony_cli
|
|
|
|
UI only. Parse argv, prompt, render. Calls [`harmony_app`](../harmony_app) or
|
|
[`harmony`](../harmony). Does not compose Scores or talk to clusters itself.
|
|
|
|
## Two front-ends
|
|
|
|
**Application delivery** — `harmony_cli::app::app_main`:
|
|
|
|
```text
|
|
cargo run -p <your-deploy-crate> -- ship --context production --tag $SHA
|
|
```
|
|
|
|
`--context` (or `HARMONY_CONTEXT`) is required. Verbs: `build`, `publish`,
|
|
`ship`, `deploy`, `status`, `logs`. `K8sAnywhereTopology` here is the control
|
|
plane (kube apply), not “the app runs on Kubernetes”.
|
|
|
|
**Generic Score runner** — `harmony_cli::run`:
|
|
|
|
```text
|
|
cargo run --bin example-cli -- --help
|
|
```
|
|
|
|
List / filter / confirm / interpret Scores. Interactive TUI when built with
|
|
`tui` (`cargo run -p example-tui`).
|
|
|
|
Architecture: [`harmony_app/README.md`](../harmony_app/README.md).
|