You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for what might be too much info, but I can't figure out if the module/parser are enforcing rules I simply don't understand, if the parser is overly aggressive -- OR if quoting to escape parser errors is not operating as expected.
Error: Invalid command syntax. Could not parse: /subsystem=messaging/hornetq-server=default/jms-queue=DLQ:add(entries=[queue/DLQ])
Failure reason: Expected one of [a-zA-Z0-9_.-@$#], ', ', ']' at line 1, column 77 (byte 77) after (entries=[queue
Error: /Stage[main]/Profiles::Hdap_api/Wildfly::Cli[add DLQ queue]/Wildfly_cli[add DLQ queue]/executed: change from false to true failed: Invalid command syntax. Could not parse: /subsystem=messaging/hornetq-server=default/jms-queue=DLQ:add(entries=[queue/DLQ])
Error: Invalid command syntax. Could not parse: /subsystem=messaging/hornetq-server=default/connection-factory=InVmConnectionFactory:add(connector={in-vm=>undefined}, entries=[java:jboss/ConnectionFactory])
Failure reason: Expected one of [a-zA-Z0-9_.-@$#], ', ', ']' at line 1, column 133 (byte 133) after (connector={in-vm=>undefined}, entries=[java
case 3, quoting everything
in both cases I can get passed the CLIParser error by putting the values in quotes:
Fair warning: I am using commits from these two PRs:
parser.failure_reason
when there's a failure. #242 ( increased CLIParser debug output )$
in treetop parsed strings. #241 ( fixes @, $, and # for identifiers )Sorry for what might be too much info, but I can't figure out if the module/parser are enforcing rules I simply don't understand, if the parser is overly aggressive -- OR if quoting to escape parser errors is not operating as expected.
case 1 , slashes ( / )
wildfly::cli { 'add DLQ queue':
command => '/subsystem=messaging/hornetq-server=default/jms-queue=DLQ:add(entries=[queue/DLQ])',
unless => '(outcome == success) of /subsystem=messaging/hornetq-server=default/jms-queue=DLQ:read-resource',
}
Error: Invalid command syntax. Could not parse: /subsystem=messaging/hornetq-server=default/jms-queue=DLQ:add(entries=[queue/DLQ])
Failure reason: Expected one of [a-zA-Z0-9_.-@$#], ', ', ']' at line 1, column 77 (byte 77) after (entries=[queue
Error: /Stage[main]/Profiles::Hdap_api/Wildfly::Cli[add DLQ queue]/Wildfly_cli[add DLQ queue]/executed: change from false to true failed: Invalid command syntax. Could not parse: /subsystem=messaging/hornetq-server=default/jms-queue=DLQ:add(entries=[queue/DLQ])
case 2, colons (:)
wildfly::cli { 'add connection-factory':
command => '/subsystem=messaging/hornetq-server=default/connection-factory=InVmConnectionFactory:add(connector={in-vm=>undefined}, entries=[java:jboss/ConnectionFactory])',
unless => '(outcome == success) of /subsystem=messaging/hornetq-server=default/connection-factory=InVmConnectionFactory:read-resource',
}
Error: Invalid command syntax. Could not parse: /subsystem=messaging/hornetq-server=default/connection-factory=InVmConnectionFactory:add(connector={in-vm=>undefined}, entries=[java:jboss/ConnectionFactory])
Failure reason: Expected one of [a-zA-Z0-9_.-@$#], ', ', ']' at line 1, column 133 (byte 133) after (connector={in-vm=>undefined}, entries=[java
case 3, quoting everything
in both cases I can get passed the CLIParser error by putting the values in quotes:
...
"java:jboss/ConnectionFactory"
"queue/DLQ"
...
edit: markdown won't seem to properly escape this ( yay irony ) , but what ends up in the XML is
'&' + 'quot;'
anywhere a double quote was in the wildfly::cli command
The text was updated successfully, but these errors were encountered: