-
Notifications
You must be signed in to change notification settings - Fork 23.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
authorized_key messes up options when using comma-separated from= list in key_options #5032
Labels
bug
This issue/PR relates to a bug.
Comments
ghost
assigned jimi-c
Nov 23, 2013
@jimi-c all yours |
test patch:
|
Works better, but not completely fixed (still breaks my existing playbooks). Additional options are not parsed correctly:
includes additional options within double quotes:
If additional options are placed before from list, like
The resulting authorized_key entry is fine:
|
jctanner
added a commit
that referenced
this issue
Dec 2, 2013
authorized_key module: rewrite options to dict parser, fixes #5032
jimi-c
pushed a commit
that referenced
this issue
Dec 6, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When specifying multiple patterns in the "from=" options for a key (like for example from="1.2.3.4,5.6.7.8."), the option parsing breaks for both the new key_options param as well as specifying the options directly in the key. This also breaks existing playbooks which worked for version <1.4.
results in following entries written to authorized_keys file
which should actually result in
$ ansible --version
ansible 1.4
Only difference in authorized_key module to devel branch is commit 32986c4, though this version just breaks differently, resulting authorized_keys file is
Specifying multiple host-patterns in a comma-separated list in the "from" option is documented in the man-page of authorized_keys:
The text was updated successfully, but these errors were encountered: