CloudMonkey should obey the standard rules for exit statuses. It would help especially with error detection from async jobs. If an error result is returned, non-zero exit status. Better than analyzing the JSON contents programmatically anyway.
On Wed, Mar 26, 2014 at 4:55 PM, ilya musayev <ilya.mailing.li...@gmail.com>wrote: > Hi Rohit, > > What is your thought on tracking exit code of CloudMonkey, as it stands - > even if CloudMonkey prints "Error:" message, no exit code is passed back to > a shell. > I know this may conflict if someone is using interactive shell, but > perhaps we can have a batch mode that can push exit codes to a shell? > > One other suggestion, as it stands if i do list zone (or any other > object), i get a list of 10-20 parameters, while i can grep through what i > need, it is rather painful and in some cases - grep just does not work > because of funky unseen chars i assume. It would be nice to have on option > that only prints user chosen parameters. > > Example, cloudmonkey list zones :print id,dns,something-else - or any > other way - as long as we get this functionality. > > Thanks > ilya >
