On 02.06.16 18:54 Brian Coca wrote: > modules don't read args, ansible does, then passes them to the module, > since the shell module is 'free form' there is really nothing to validate > against, since what you are passing can work in a shell .. there is no > error thrown either.
I'll reword my thought: If ansible is doing the parsing, it already distinguishes between the two syntax methods (the one with one line and all stuff and the other one where there is a line containing 'args:' and some more lines). IMHO it should note that as soon as the 'args:' appears, everything after that should be in declarative syntax (foo: bar) and every line not containing a colon is wrong syntax. 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/57506E8D.2020407%40ojkastl.de. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
