shc hud
open the platform TUI (k9s’s UX over the SHC provider)
Reference for the hud command. Source: cli/hud.go,
provider: pkg/x9sprov/.
shc hud opens x9s, k9s’s exact terminal UX (: command bar, live
tables, / filter, d describe, l log follow, s shell,
Shift-F port-forward, a actions, e edit, ctrl-n create,
x reveal a secret, c copy), over this platform instead of a
Kubernetes cluster.
Secrets never sit in a table, a document or the history. :secrets
shows each value as ••••••; x fetches the focused one and shows it
in place until x again, and c copies it. c writes OSC 52 first, so
over SSH on a node the value lands on your own clipboard (inside tmux,
set -g set-clipboard on), then pbcopy, wl-copy or xclip where one can
run. Passwords and secret values are typed into masked fields, and a
new secret (ctrl-n on :secrets) is a form, not a YAML file.
Installs and updates are typed forms too. i on an :apps row, or
ctrl-n on :deployments (pick the app first), asks where the deployment
goes and then one field per app variable, prefilled with the package
default; e on a deployment asks the same fields prefilled with what it
runs now. The confirm prints the shc install or shc update those
answers make, and after an install the HUD opens the new deployment’s
services, which fill in as its containers start.
Every argument is passed through to the embedded provider
(--url, --token, --tenant, --daemon-socket, …; see
shc hud --x9s-serve --help). Config lives under
<user-config-dir>/shc9s unless $K9S_CONFIG_DIR is set.
The command obeys the active shc ctx cluster the same way every
other verb does, and opens on :deployments at the shc ctx tenant,
environment and stack. None of the three is a pin: u on :tenants, the
number keys and :stacks switch away. An explicit --tenant (which does
pin), --environment or --stack, or $SHC_TENANT, $SHC_ENVIRONMENT or
$SHC_STACK, wins over the context. An untagged build refuses with X501216HUDTUI.