Summary
Tracking issue bundling the recipe / validate CLI UX problems reported in #1361. These are small, independent, and cohesive (same area) — fixable in one or two PRs.
The big symptom in #1361 (the repeated chainsaw: no such file or directory) is already fixed in v0.15.0 via #1252 (in-process chainsaw executor); the reporter hit it on a pre-release source build. This tracker covers only the remaining UX items.
Items
| # |
Problem |
Location |
Fix sketch |
| 1 |
validator completed status=failed printed green — should be red |
pkg/logging/cli.go colors by log level, not status |
Log failed validators at slog.LevelError (or color by a status attr) |
| 2 |
recipe prints 18 components but never lists them |
pkg/cli/recipe.go:232 |
List component names (debug-level full list, or a summary line) |
| 3 |
Not obvious that recipe/validate don't hit a live cluster |
pkg/cli/recipe.go, pkg/cli/validate.go |
One-line banner stating offline vs. cluster mode |
| 4 |
-o table output garbled (jsonPath + raw, unindented/unescaped YAML mix) |
pkg/serializer/writer.go:207 |
Fix nested-value rendering or restrict table to flat scalars |
| 5 |
any criteria values shown with no explanation (good/bad/autodetect?) |
pkg/cli/consts.go:42 |
Annotate any as "wildcard / unconstrained" in output |
| 6 |
agent log streaming skipped: pod did not become ready — which pod? |
pkg/snapshotter/agent.go:208 |
Add namespace/jobName attrs (already in scope on AgentConfig) |
| 7 |
Error says "pass --node-selector or --require-gpu" but not exact syntax |
pkg/snapshotter/agent.go:228 |
Show a concrete example (flags are separate, repeatable key=value) |
| 8 |
validate failure doesn't name failing resources inline; only buried in JSON |
validators/deployment/expected_resources.go:165 |
Surface a concise per-component failure summary to the CLI |
Notes
These can be split across PRs as convenient; items 1, 6, 7, 8 are the highest-impact for "I am lost as a user" feedback.
Split out from #1361.
Summary
Tracking issue bundling the
recipe/validateCLI UX problems reported in #1361. These are small, independent, and cohesive (same area) — fixable in one or two PRs.The big symptom in #1361 (the repeated
chainsaw: no such file or directory) is already fixed in v0.15.0 via #1252 (in-process chainsaw executor); the reporter hit it on a pre-release source build. This tracker covers only the remaining UX items.Items
validator completed status=failedprinted green — should be redpkg/logging/cli.gocolors by log level, not statusslog.LevelError(or color by astatusattr)recipeprints18 componentsbut never lists thempkg/cli/recipe.go:232recipe/validatedon't hit a live clusterpkg/cli/recipe.go,pkg/cli/validate.go-o tableoutput garbled (jsonPath + raw, unindented/unescaped YAML mix)pkg/serializer/writer.go:207anycriteria values shown with no explanation (good/bad/autodetect?)pkg/cli/consts.go:42anyas "wildcard / unconstrained" in outputagent log streaming skipped: pod did not become ready— which pod?pkg/snapshotter/agent.go:208namespace/jobNameattrs (already in scope onAgentConfig)--node-selectoror--require-gpu" but not exact syntaxpkg/snapshotter/agent.go:228key=value)validatefailure doesn't name failing resources inline; only buried in JSONvalidators/deployment/expected_resources.go:165Notes
These can be split across PRs as convenient; items 1, 6, 7, 8 are the highest-impact for "I am lost as a user" feedback.
Split out from #1361.