At 2014-09-12 15:14:42 -0400, [email protected] wrote:
>
> Changing all the examples would make very good since for the short
> term, though I believe we can also deal with fixing the \n issue.
OK, I'll submit a pull request to change the examples.
> I'm not aware of anything wrong with the key parameter, usually that's
> one entry per line anyway, and also only used with a single line, but
> multiple lines don't hurt that file IIRC.
No, the problem with authorized_key's key= is not multiple lines, but
quoting. For example, if you want to install the following key:
from="1.2.3.4",command="rsync --server -logDtpre.iLsf --delete .
foo/",no-pty,no-port-forwarding,no-X11-forwarding,no-agent-forwarding ssh-rsa …
using something like:
authorized_key: user=foo key="{{ lookup('file', …) }}"
Then you get:
fatal: [localhost] => A variable inserted a new parameter into the
module args. Be sure to quote variables if they contain equal signs (for
example: "{{var}}").
This has come up a few times, including in the bug report that I linked
to in my earlier post. For this problem, too, using the "key: value"
syntax makes the problem go away. So I'll change those examples too.
Independent of that, if you want to outline your approach to solving the
\n and quoting problems, I'd be happy to work on them.
-- 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/20140919043947.GB16026%40toroid.org.
For more options, visit https://groups.google.com/d/optout.
