[jboss-jira] [JBoss JIRA] (WFCORE-1743) Unable to force CLI to execute a low level command

[Alexey Loubyansky (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285413#comment-13285413 ] 

Alexey Loubyansky commented on WFCORE-1743:
-------------------------------------------

I see your point. The CLI, though, is not actually retrieving the description for validation purposes but to actually complete building the operation request since there are some usability features that require the description. Such as replacement of certain user-friendly parameter values with the values that actually should be sent. For example replacing file system paths with attached streams (user specifies file system paths as parameters while the CLI, according to the operation parameter descriptions, turns those into attachments).

I guess, in the CLI, in case the description could not be retrieved, instead of throwing an error, we could simply ignore it, do not replace anything and send the request as it was literally typed-in.

> Unable to force CLI to execute a low level command
> --------------------------------------------------
>
>                 Key: WFCORE-1743
>                 URL: https://issues.jboss.org/browse/WFCORE-1743
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 3.0.0.Alpha5
>            Reporter: Brian Stansberry
>            Assignee: Alexey Loubyansky
>             Fix For: 3.0.0.CR1
>
>
> I cannot get this operation to execute, even if I set validate-operation-requests to false in jboss-cli.xml:
> {code}
> [standalone at embedded /] /subsystem=datasources/bogus=*:read-resource-description
> Failed to get the list of the operation properties: "WFLYCTL0030: No resource definition is registered for address [
>     ("subsystem" => "datasources"),
>     ("bogus" => "*")
> ]"
> {code}
> It is important that the CLI allows users to send whatever low level ops they wish to the server if they turn off verification. The server validates requests itself, and in some cases can be coded to be lenient about things (e.g. to let previous 'wrong' things work.) We don't want the CLI to get in the way of that by doing client side validation that cannot be turned off.
> Problem seems to be this in the Util class:
> {code}
>     public static ModelNode toOperationRequest(CommandContext ctx,
>             ParsedCommandLine parsedLine, Attachments attachments)
>             throws CommandFormatException {
>         return toOperationRequest(ctx, parsedLine, attachments, true);
>     }
> {code}
> That 'true' param results in the CLI trying to do a background read-operation-description and failing the op if unsuccessful.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)