[jboss-jira] [JBoss JIRA] (WFCORE-418) Input/Output Formats Should Be Standard Formats (json/yaml/etc)
Jean-Francois Denise (JIRA)
issues at jboss.org
Wed Jan 11 08:35:02 EST 2017
[ https://issues.jboss.org/browse/WFCORE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Francois Denise reassigned WFCORE-418:
-------------------------------------------
Assignee: Jean-Francois Denise (was: Alexey Loubyansky)
> Input/Output Formats Should Be Standard Formats (json/yaml/etc)
> ---------------------------------------------------------------
>
> Key: WFCORE-418
> URL: https://issues.jboss.org/browse/WFCORE-418
> Project: WildFly Core
> Issue Type: Enhancement
> Components: CLI
> Environment: RHEL 6.4, x86_64
> Reporter: Chris Pitman
> Assignee: Jean-Francois Denise
> Labels: automation, cli, configuration_management, json
>
> The purpose of the CLI is to improve automation for administrators, but the format used for data is a non-standard format that cannot be easily parsed or generated by any language.
> The format is *really* close to json, but with enough deviation to make munging it a pain: replace hash rockets (=>) with colons, undefined with null, and key value pairs ("(a => b)") with hashes ("{a : b}"). Going in the opposite direction requires some sort of cleverness to determine what is a key-value pair, which is not fun.
> The CLI should support both output and input in a standard format, so that the above hoops do not have to be jumped through.
> Steps to Reproduce:
> 1. Connect to the jboss cli
> 2. Execute "/:whoami"
> Actual results:
> {
> "outcome" => "success",
> "result" => {"identity" => {
> "username" => "$local",
> "realm" => "ManagementRealm"
> }},
> "response-headers" => {"process-state" => "reload-required"}
> }
> Expected results:
> {
> "outcome": "success",
> "result": {"identity": {
> "username": "$local",
> "realm": "ManagementRealm"
> }},
> "response-headers": {"process-state": "reload-required"}
> }
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list