(This shows the usage info for restart, even though we requested it for restart connectors)

I'm confused by this one, it still shows the wrong one, no?

> kcctl help restart connectors
Usage: kcctl restart [-hV] [COMMAND]
Restarts some connectors or a task
  -h, --help      Show this help message and exit.
  -V, --version   Print version information and exit.
Commands:
  connector, connectors  Restarts the specified connector(s)
  task                   Restarts the specified connector or task

• Why does it mention the task sub-command, when displaying the help for the connectors sub-command? It seems that output above is actually for the restart command?
• Unrelated, but it seems the help message for task is wrong, it should just say "Restarts the specified task"?

Even though the -V flag is included in the usage summary for every command, it doesn't actually do anything when invoked with a command/subcommand (e.g., kcctl delete -V). When this happens, nothing is printed and the exit status is zero.

Hum, yeah, that's a bit weird.

A bit of noise is added to the usage summary for every command. Commands that accepted a single argument or flag now have info on two additional flags (-h and -V), one of which is a no-op.

The -h seems justified, but -V not so much?

Autocomplete support for the help command is completely wiped. We can probably restore it if that's a dealbreaker fro this PR.

Not a deal-breaker if it's only for the help command. Maybe though we should get rid of it and only support option 3 (-h, --help)?

I jumped the gun implementing this. Going to mark as a draft and continue the discussion on #363 until we've settled on an ideal syntax; you raised some good points there that deserve to be addressed before we spend time on code review. Thanks for the rapid turnaround though! 😄

Got rid of the extraneous -V flag. Took a little bit of legwork but hopefully the approach of adding a mixin to each command class isn't too brittle. If it is, I can try to look into more automatic/magical approaches that don't require per-command changes.

Not a deal-breaker if it's only for the help command. Maybe though we should get rid of it and only support option 3 (-h, --help)?

Correct, it's only for the help command. I personally really like the help <command> <subcommand> syntax so I'll look into bringing back autocomplete for it (hopefully including nested subcommands!)... hoping we can all be happy with the result here 😄

I'm confused by this one, it still shows the wrong one, no?

Sorry, missed this comment earlier! Was a copy+paste error on my part. I've updated the description with the correct output, after verifying that it accurately reflects what the CLI emits after being built with the latest commit for this PR.

Unrelated, but it seems the help message for task is wrong, it should just say "Restarts the specified task"?

Yeah, good catch! I'll add it to this PR tomorrow if there are no objections.

Sweet, this LGTM overall to me. IIUC, there's two remaining loose ends:

• Wrong message for restart task (+1 for adding this to this PR)
• Completion broken for help command

Anything else?

I think that's it!

With the latest commit, I fixed the restart task help description, and yesterday I "fixed" the help autocompletion. It's broken for nested subcommands, but works for top-level commands, which matches the logic on the current main. More info in the description.

I want to try to get autocomplete working for nested subcommands with help at some point, but don't think that should be a blocker. If you agree, I think we can merge this 🎉

Sounds good, can you just log a follow-up issue for the nested subcommand help auto-completion?

Applied. Thanks a lot, @C0urante!

Thanks Gunnar! Filed #370 as a follow-up for autocompletion of nested subcommands.