mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-09-13 19:17:52 +00:00
6864a5547a
...plus a few others. And fixes to actual parsing. If a command's usage message includes '...' in the argument list, assume it can take unlimited arguments. Nothing we can check. For all others, though, the ALL-CAPS part on the right-hand side of the usage message will define an upper bound on the number of arguments accepted by the command. So in our 'podman --help' test, generate N+1 args and run that command. We expect a 125 exit status and a suitably helpful error message. Not all podman commands or subcommands were checking, so I fixed that. And, fixed some broken usage messages (all-caps FLAGS, and '[flags]' at the end of 'ARGS'). Add new checks to the help test to prevent those in the future. Plus a little refactoring/cleanup where necessary. Signed-off-by: Ed Santiago <santiago@redhat.com> |
||
|---|---|---|
| .. | ||
| attach.go | ||
| checkpoint.go | ||
| cleanup.go | ||
| commit.go | ||
| container.go | ||
| cp.go | ||
| create.go | ||
| diff.go | ||
| exec.go | ||
| exists.go | ||
| export.go | ||
| init.go | ||
| inspect.go | ||
| kill.go | ||
| list.go | ||
| logs.go | ||
| mount.go | ||
| pause.go | ||
| port.go | ||
| prune.go | ||
| ps.go | ||
| restart.go | ||
| restore.go | ||
| rm.go | ||
| run.go | ||
| runlabel.go | ||
| start.go | ||
| stats.go | ||
| stop.go | ||
| top.go | ||
| unmount.go | ||
| unpause.go | ||
| utils.go | ||
| wait.go | ||