In the current Ansible setup, you can have 1 file in defaults (i.e.
defaults/main.yml) and it is used for all hosts that run that task, no
matter what the host.
In our use case, we have found it would be highly advantageous to be able
to have os-specific and release-specific defaults files. For
I found this post
(http://stackoverflow.com/questions/29276198/ansible-how-to-construct-a-variable-from-another-variable-and-then-fetch-its-v)
and was hoping to find a way to cope with it.
To sum up though, basically I have a situation where I'd like to get the
value of a value of a variable.
ntence #2 about inheritance, as I'm unclear how
>>> inheritance applies to directories.
>>>
>>> "It would be nice if one role could inherit another's directory
>>> structure."
>>>
>>> Looking at the two YAML files, I see both
>
> I'm having trouble parsing this one, sorry.
>
> Would it be possible to see a git repo or something for this ticket that
> minimally reproduces the question?
>
>
> On Tue, Jul 29, 2014 at 12:57 PM, Mike Ray > wrote:
>
>> As of 1.6.2 (yes, not quite current,
no_log: True
>
>
>
>
>
> On Mon, Aug 4, 2014 at 12:21 PM, Mike Ray > wrote:
>
>> Ansible's logging to the system log is pretty sweet.
>>
>> However, there are occasions when I'd like to repress it for security
>> concerns.
>>
>
I can't say as I'm familiar with the nested construction, but at least part
of the problem is given to you:
*msg: this module requires key=value arguments*
(['dest=/etc/pam.d/system-auth-ac', 'regexp=^auth.*pam_faillock\\.so\\
auth.*\\ deny=3\\ unlock_time=604800\\ fail_interval=900',
'inserta
Ansible's logging to the system log is pretty sweet.
However, there are occasions when I'd like to repress it for security
concerns.
Specifically, when using the file module and the contents flag, whatever
"contents" is set to, will show up in the syslog in plain text.
For example, when copyin
I've also run into this issue and haven't picked the best way to deal with
it yet.
You can always run that command via the shell module. Occasionally commands
get a little gross and you'll have to add so many escape characters and
quotes that even you can't tell what's going on. If that happens
aps I can re-implement it.
Mike Ray
On Thu, Jul 31, 2014 at 3:16 PM, Michael DeHaan wrote:
> Remote backups?
>
> Honestly haven't had time to attack. I'll bump the priority though so it
> doesn't get lost in the shuffle -- it's a good idea -- and an OLD id
What is the status of this? My team would find a feature like this
immensely helpful.
It would be additionally useful if you could force it to only maintain X
backups in said backup directory.
I see nothing in the changelogs about this.
On Saturday, October 12, 2013 12:44:52 PM UTC-5, Vadim S
g for this ticket that
> minimally reproduces the question?
>
>
> On Tue, Jul 29, 2014 at 12:57 PM, Mike Ray > wrote:
>
>> As of 1.6.2 (yes, not quite current, though I did not see anything in the
>> changelog that addressed this), when using roles, each role is call
As of 1.6.2 (yes, not quite current, though I did not see anything in the
changelog that addressed this), when using roles, each role is called
relative to its own directory.
E.g.
playbook1.yml :
---
- hosts: '{{ hostlist }}'
remote_user: root
roles:
- role: apache2
- role: mysq
12 matches
Mail list logo
