Link to @that70schris's main issue: warpdotdev/warp#12693
talosctl (the Talos Linux CLI for out-of-band management of Kubernetes nodes) has no completion spec yet — command-signatures/json/ covers the adjacent kubectl and helm, but not talosctl. Warp's Oz triage on the main issue confirmed this is a native completion feature gap and marked it ready-to-implement.
Since talosctl is Cobra-based like kubectl/oc, the plan mirrors the existing precedent:
- Static spec walked from talosctl v1.13.6's command tree (106 nodes, 49 top-level commands)
- A
talosctl_builtin_completion generator delegating dynamic completions (config contexts, node services, resource types, --nodes/--endpoints/--context values) to the CLI's hidden Cobra __complete command, same approach as oc_builtin_completion in oc.rs
filepaths/folders templates on path-like flags (--talosconfig, --file, --*-path, --*-dir, …)
Implementation is ready; PR to follow. @lucieleblanc could you add ready-to-implement when you get a chance (for the Oz review gate)? 🙏
Link to @that70schris's main issue: warpdotdev/warp#12693
talosctl(the Talos Linux CLI for out-of-band management of Kubernetes nodes) has no completion spec yet —command-signatures/json/covers the adjacentkubectlandhelm, but nottalosctl. Warp's Oz triage on the main issue confirmed this is a native completion feature gap and marked itready-to-implement.Since
talosctlis Cobra-based likekubectl/oc, the plan mirrors the existing precedent:talosctl_builtin_completiongenerator delegating dynamic completions (config contexts, node services, resource types,--nodes/--endpoints/--contextvalues) to the CLI's hidden Cobra__completecommand, same approach asoc_builtin_completioninoc.rsfilepaths/folderstemplates on path-like flags (--talosconfig,--file,--*-path,--*-dir, …)Implementation is ready; PR to follow. @lucieleblanc could you add
ready-to-implementwhen you get a chance (for the Oz review gate)? 🙏