On Friday, 26 December 2014 05:05:33 UTC-5, Catalin Costache wrote:
>
> Yaml has a notation for multiline string. I set user data like so:
>
> user_data: |
> #!/bin/bash
> echo "Defaults:{{admin_user}} !requiretty" > /etc/sudoers.d/
> disable_requiretty
>
I'm having trouble using th
On Mon, Apr 21, 2014 at 7:23 PM, Michael DeHaan wrote:
> If you would ever like to report a crash, including the "result" of the
> crash is
>
needed to understand the context.
> Can you please paste the result you are receiving?
>
I'm not sure why you want the backtrace; it's already fixed in 1.
I've got a role that works in 1.6 but crashes in 1.5. (My guess is that
this fixes it: https://github.com/ansible/ansible/commit/2a976a)
The crashing task is this:
- authorized_key: user={{ item|basename }} key="{{ lookup('file', item) }}"
with_fileglob:
- "../../../../keys/*"
The role
I have a task that works on devel but not on 1.5.4. I assume it's because
of https://github.com/ansible/ansible/commit/2a976a
- authorized_key: user={{ item|basename }} key="{{ lookup('file', item) }}"
with_fileglob:
- "../../../../keys/*"
We have ansible installed on all our production
Thanks for your suggestions.
I think my approach will be to use the template file to create the
configuration only if it doesn't exist, and then use config set/rewrite to
set any configuration variables that may change over the project lifetime.
Ansible 1.6 includes some more options to the redis
How do people generally set up Redis through ansible?
Right now we're using the fairly standard approach of templating the
configuration files, and using a notify handler to restart redis whenever
the configuration file changes.
The problem with this is that Redis often rewrites its configurati
