[
https://issues.apache.org/jira/browse/CLOUDSTACK-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692887#comment-13692887
]
Rohit Yadav commented on CLOUDSTACK-1875:
-----------------------------------------
This fix was not commited on 4.1 because the branch was previously frozen. But
I'll add the fix/feature on 4.1 branch soon. Once the cloudmonkey migration
happens successfully things will be less confusing.
> Add JSON output into cloudmonkey
> --------------------------------
>
> Key: CLOUDSTACK-1875
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1875
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Cloudmonkey
> Affects Versions: 4.1.0, Future
> Reporter: Justin Grudzien
> Assignee: Justin Grudzien
> Priority: Minor
> Labels: newbie, patch
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Data in JSON format is very easy to read for large data sets. Presently,
> cloudmonkey supports tabular or line based output and looking at large output
> tends to be problematic. By adding JSON output with filtering, a user can
> more easily process and consume data. The following items should make
> cloudmonkey data more easily consumable:
> 1. Need to format empty return messages with proper JSON messaging.
> 2. Need to standardize JSON output messaging.
> A. Add return code [Error|Success] to all calls.
> B. Add called API verb.
> 3. Count is not decreased in output set when filtering completely eliminates
> a result.
> 4. JSON printing needs to be implemented manually to support colors. Right
> now json.dumps() pretty prints the output and changing the keys to support
> colors is problematic.
> 5. Color tagging needs to be added to JSON printing.
> 6. Error messages need to have proper JSON formatting.
> 7. Make color a passable option to a command instead of a config parameter.
> (i.e. list users account=grudzien color=true)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
