]
Brian Stansberry commented on WFCORE-1743:
------------------------------------------
Another reason it's important that users can configure the CLI to be lenient about
sending low level ops is it's very helpful to us server developers in analyzing server
behavior. If we can't do this we'd have to write custom clients to experiment,
which is impractical. I hit this issue while trying to investigate solutions to
WFCORE-1737.
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@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.