Documentation
¶
Overview ¶
Package run implements the `kuke run` verb. The `-f <file>` form parses a single-cell YAML doc and idempotently create-and-starts the cell; the `-b` form resolves a daemon-stored CellBlueprint, and the positional `<config>` form resolves a daemon-stored CellConfig — both walk the same create-or-attach state machine. The legacy `-p/--profile` form (client-side CellProfile loader under $HOME/.kuke/profiles.d) was removed in #626 — it is intercepted at flag-parse time and replaced with a migration pointer.
`kuke run` attaches to the cell's attachable container by default, matching `docker run` and `kubectl run -it`. Pass `-d/--detach` to return immediately after start without attaching.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func NewRunCmd ¶
NewRunCmd builds the `kuke run` cobra command — the docker-model fused verb (epic:cell-identity #1025). The optional positional names an existing cell to start + attach; `--from-blueprint` / `--from-config` / `--clone` create + start + attach a fresh cell, delegating the create half to the same materialization the un-fused `kuke create cell` runs; `-f` create-or-attaches a cell from a YAML manifest. Exactly one source is required. By default the CLI drops the operator into the cell's attachable terminal after start; `-d/--detach` opts out of the post-start attach.
Types ¶
type MockControllerKey ¶
type MockControllerKey struct{}
MockControllerKey is used to inject a mock kukeonv1.Client via context in tests.
type MockRunKey ¶
type MockRunKey struct{}
MockRunKey is used to inject a mock runFn via context in tests, so the real pkg/attach.Run (which would open a TTY and connect to a real control socket) is bypassed.
Source Files