CLI doesn't validate -switch in a guaranteed manner

What steps will reproduce the problem?
1. conf ls -p -duster (that's a d on purpose btw)
2. hosts -dave
3. cluster status -roger

Basically make up a switch, and as long as the required switches exist, you can 
reproduce

What is the expected output? What do you see instead?

If a command is attempted with a switch that is invalid, the entire command 
should fail with a suitable warning after validation.  Currently now it'll run 
the rest of the command and ignore the invalid switch.

So if for example I have a typo and do a "deploy -duster" - I'm going to get 
bizarre ressults that may not be apparent.  From an Operational perspective, 
I'd expect the deploy (in this case) to fail before it starts, as I'm talking 
rubbish and Corus should want to understand my exact requirements, not make 
assumptions.

What version of the product are you using? On what operating system?

Exists from at least 4.0.1 (if not before), and is valid in 4.2RC5

Please provide any additional information below.

Original issue reported on code.google.com by c...@maxnet.eu.org on 18 Jul 2014 at 7:07

yduchesne / sapia

CLI doesn't validate -switch in a guaranteed manner #16