[ https://issues.jboss.org/browse/WFLY-2946?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky commented on WFLY-2946: ----------------------------------------- So, I don't think it's a good idea to just not validate the arguments just because the batch mode is on. Even as an exception for the cd. Validation exists for a reason (it was actually requested by the users) and, IMO, it still makes sense in the batch mode too. So, I propose, as a compromise for this case to add an argument to the cd (or perhaps even make it a global one supported by all the cli commands), e.g. --no-arg-validation or something shorter but clear, which would indicate that the user is actually asking to not validate the arguments. Because in this case the user does know that the address that is being entered does not exist at this point. Making it a global argument for all the commands though, should have as a consequence the fact that the non-validated commands might have unpredicted results (in their behavior and the effect on the management model). And that would be the user's responsibility. The cd command in this sense is really harmless. So, perhaps, as a start this kind of argument could be added only to the cd. -- This message was sent by Atlassian JIRA (v6.2.6#6264)