cursus.cli.steps_cli¶
CLI for inspecting a step’s connection / I-O view (FZ 31e1d3d follow-up).
Under the Strategy + Facade design a step’s builder is a near-empty shell — the container
source/destination paths, the runtime property-path references, and the nested training-channel
fan-out are no longer visible in a readable builder class; they live in the .step.yaml + the
bound handler. cursus steps io <name> renders that hidden wiring view:
- cursus steps io XGBoostTraining
# per dependency: logical_name | container path | required | type, plus the SageMaker # training channels it fans into (train/val/test); per output: container path + # property_path runtime reference.
- cursus steps io RiskTableMapping –job-type validation
# resolve the job_type variant (different required-flags / compatible_sources).
cursus steps io XGBoostTraining –format json
Reads cursus.steps.interfaces.io_view.describe_step_io — the same interface + handler the
builder uses, so the view can never drift from what the step actually wires. Read-only.