sopel
commented
10 years ago :information_source: worth noting that (amongst other related improvements), the http://aws.amazon.com/cli/ meanwhile features an extremely powerful JSON output plus result shaping query functionality, which mostly obsoletes the jq option mentioned above, see e.g.:
- Controlling Command Output from the AWS Command Line Interface - official documentation
- [Using aws-cli --query Option To Simplify Output]() - Eric Hammond's instructive example
This should be mirrored here accordingly, which again calls for reconsidering the entire project design/purpose though (see #44).
Console output and logging have evolved in an ad hoc fashion and are severely inconsistent accordingly, see e.g. init.py#L69 and describe-stacks.py#L34.
Given the current use cases are automation related, there had also been considerations to facilitate JSON console output to allow command output chaining/usage via the Unix pipeline pattern and respective JSON command processors like e.g. jq.
A possible implementation would likely involve use of Multiple handlers and formatters and Logging to multiple destinations.
This should be revisited to ease library evolution and maintenance.