-
Enhancement
-
Resolution: Done
-
Major
-
None
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" =>
}
Expected results:
{
"outcome": "success",
"result": {"identity": {
"username": "$local",
"realm": "ManagementRealm"
}},
"response-headers":
}
- is related to
-
WFLY-3340 Authentication "module-options" inconsistently hash vs list of key/values
- Closed
- relates to
-
WFCORE-3363 CLI to output JSON
- Resolved