]
Brian Stansberry moved WFLY-3339 to WFCORE-418:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-418 (was: WFLY-3339)
Affects Version/s: (was: JBoss AS7 7.1.1.Final)
Component/s: CLI
(was: CLI)
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: Alexey Loubyansky
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"}
}