On 02.06.16 00:35 Brian Coca wrote: > args won't give you an error in the case you showed as you passed a string > to the shell module which allows for arbitrary strings (shell commands). To > the shell that would have appeared as setting a variable inline or an extra > parameter.
But I would have thought that as soon as an 'args:' appears, the shell module should get that the following is syntax-with-colon and throw an error otherwise. Or do you mean that creates=foo could be a valid argument? But all arguments to the shell module should declare something (a=b), not just switch something on or off (disable_foo). Johannes -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/574FDF5F.4000002%40ojkastl.de. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
