[ https://issues.jboss.org/browse/WFLY-2403?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2403: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com&gt; made a comment on [bug 970679|https://bugzilla.redhat.com/show_bug.cgi?id=970679] The CLI command clearly indicates the intent that the datasource be enabled: [standalone@localhost:9999 /] data-source add --name=Test2 --driver-name=h2 --enabled=true --jndi-name=java:jboss/datasources/Test2 --connection-url=jdbc:h2:mem:test2;DB_CLOSE_DELAY=-1 A big part of the point of high level CLI commands is they should hide all the low level details from the user. So if the intent of the high level command was the datasource should be enabled in the runtime when the command returns, there's a bug that needs fixing. There's a general issue with CLI high level commands not providing all the response data to the user that low level commands do. But that's beyond the scope of this particular issue. @Martin: Is the Comment 10 behavior a regression, or something that never behaved the way you expect? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira