Skip to content

Add completion spec for talosctl (Talos Linux CLI) #293

Description

@maxmilian

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)? 🙏

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions