After any syntactically correct pulp-admin command, you can type any string you want and the command will still run.

We should have better input validation and throw up a help message instead in this case.  The reason being is that we don't know if the arbitrary string was meant to be another option, and now we've executed a command the user didn't intend.

Here's an example. I wanted to sync a repo in the foreground.  I typo'd "-F" as "0F":

# pulp-admin repo sync --id candlepin-x86_64 --limit 5 0F

The command still ran, but was sync'ing in the background.

This seems to apply to any command:

$ pulp-admin repo list monkies

will do a repo list.