Why
sfputil groups mutating commands by topic - sfputil lpmode {on,off} and sfputil firmware {run,commit,upgrade,download,unlock,target} - but the read-side equivalents only exist under a separate top-level show group (sfputil show lpmode, sfputil show fwversion). A user running sfputil lpmode --help or sfputil firmware --help sees only mutating actions and has no signal that an inspection command exists elsewhere.
This will help with discoverability: --help becomes self-contained — the inspection command is reachable from the same help output as the verbs.
Proposal
I propose to expose the existing read commands as aliases under their topic groups:
sfputil lpmode show — same behavior as sfputil show lpmode
sfputil firmware show— same behavior as sfputil show fwversion
The originals should remain in place.
Why
sfputilgroups mutating commands by topic -sfputil lpmode {on,off}andsfputil firmware {run,commit,upgrade,download,unlock,target}- but the read-side equivalents only exist under a separate top-levelshowgroup (sfputil show lpmode,sfputil show fwversion). A user running sfputil lpmode --help or sfputil firmware --help sees only mutating actions and has no signal that an inspection command exists elsewhere.This will help with discoverability:
--helpbecomes self-contained — the inspection command is reachable from the same help output as the verbs.Proposal
I propose to expose the existing read commands as aliases under their topic groups:
sfputil lpmode show— same behavior assfputil show lpmodesfputil firmware show— same behavior assfputil show fwversionThe originals should remain in place.