[ https://issues.jboss.org/browse/WFCORE-1726?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-1726: ----------------------------------------- Description: CLI doesn't support the streams attached to a response. Incremental deployment support offers today the ability to read the content of a deployment. It would be interesting to operate it from the CLI. Some resource (such as the log file) expose some attributes as stream. The following operations are returning streams: /subsystem=logging/log-file=server.log:read-attribute(name=stream) /subsystem=logging/log-file=server.log:read-resource(include-runtime) /deployment=toto:read-content(path=index.html) As we can see, streams can be located in attributes, as operation response, inside a resource. The CLI offers 2 way to approach the problem: 1) Extend the Low level operation support with a way to save/display attached streams. This would require some XML configuration and possibly UI workflow to prompt user for the right action. 2) Define a new high level command that would cope with any operation. Such command would look like: attachment save --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) --file=/my/local/path/to/file attachment display --operation=/subsystem=logging/log-file=server.log:read-attribute(name=stream) was: CLI doesn't support the streams attached to a response. Incremental deployment support offers today the ability to read the content of a deployment. It would be interesting to operate it from the CLI. On receipt of such streams, the CLI could prompt the user for actions. The prompt message would contain the type of attachement (XML, JSON, bin,...) in order for the user to choose to visualise or save the attachement to a file. This behaviour could be made configurable by a CLI configuration option. -- This message was sent by Atlassian JIRA (v6.4.11#64026)