At 2014-09-12 10:29:23 -0400, [email protected] wrote:
>
> Alternatively:
>
> copy:
> content: "{{ value }}"
> dest: foo
>
> Will pass things along without trying to go through the line-oriented
> parsing.
Yes, as I mentioned in my mail, that's the workaround I'm already using.
I do think the documentation should mention something about when to not
use key=value syntax, though.
I find copy's "content" parameter quite convenient to put things like
policy-rc.d scripts and SSL keys from ansible-vault in place. But even
if we disregard that as silly, authorized_key's "key" parameter has
exactly the same problem with parsing.
The documentation for it uses key="{{ lookup … }}" _everywhere_, and
that breaks when your key file starts with «from="12.34.45.56", …»
(which is what github issue #6294 was about).
Would you take a patch to change all the example to use key: "…"
syntax instead?
-- ams
--
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/20140912153407.GA16026%40toroid.org.
For more options, visit https://groups.google.com/d/optout.
