Think this might be a parser bug - the arguments are not parsed the same when using a nested <arg> tag under <exec>. In the code snippet below, the nested <arg> is passed as a single app, and parameters don't work.
I need a status check and the command takes about 6 parameters, so I go from a non-conditional
<exec command="/bin/command" args="-z one -k two -h three -o 'Something else'" /> to:
<arg value="-z" />
<arg value="one" />
<arg value="-k" />
<arg value="two" />
<arg value="-h" />
<arg value="three" />
<arg value="-o" />
<arg value="Something else" />
<runif status="passed" />
This could be resolved by allowing a single <args> sub-tag of <exec>, instead of only <arg> in Go. Does it still stand that when using a <runif>,
arguments have to be passed as child elements to exec, or can exec be used with args= and a runif child element?