Uncaught exception behavior

[RazzM13]

Apparently, when the cfn-lint cli executable encounters an uncaught exception during the validate command, it outputs the associated stack trace.

Perhaps it would be more consistent to output Unable to parse template! instead of the rather lengthy stack trace.

[martysweet]

Agreed. This can also be merged with issue #121 to resolve the exit code issue.

Stack traces can be useful for debugging, we still need a method to see this to work out whats gone wrong.

[RazzM13]

I've just looked at the cli's usage screen and apparently there's no flag for a debug or verbose mode. Therefore, what I am suggesting is that we perhaps add a new flag -d or -v or something similar for the additional output and that's where we would be seeing the stack trace... just a thought :)

[martysweet]

I think adding a --verbose flag would be good, this would then provide further scope if we wish to return other information to the user during runtime.