stackkit use-cases add, stackkit use-cases pick
stackkit use-cases add
Add a catalog use case to an existing standalone installation. Add a use case using the installed kit’s CUE-owned alternative and module profile defaults. Preserve existing workloads, routes, placement and storage. Persist the candidate by the current spec hash and materialize only the selected use case’s local secret slots. Existing custody is reused. No services are deployed; generate and apply the updated intent through the normal lifecycle. Native stackkit/v2alpha2 and a single standalone node/site are required.
Examples
stackkit use-cases pick
Interactively select optional use cases. List the kit-optional use cases and toggle them in the terminal. Arrow keys or j/k move the cursor. Space toggles the highlighted item. Enter confirms. Without--kit, the legacy Files, Photos and Vault selection is used.
With --kit (Basement or Cloud), choices and defaults come from the embedded CUE kit catalog. Each choice shows its standard profile minimum (CPU / RAM GiB / disk GiB). The running numeric preview includes required Core and selected default alternatives. It observes this host unless --inventory and --node select another target. Data budgets, add-ons, profile changes and resident policy need a resolved plan. This preview writes no configuration and grants no Apply admission.
--print writes the selected IDs as a comma-separated line on stdout so installers can pass them to stackkit init --use-case. Prompts go to stderr. When stdin is not a terminal, defaults are returned without a prompt; a kit preview is still printed to stderr. Unknown facts are shown as ?, never zero.
Examples