On Sunday, 31 January 2016 10:52:40 UTC, Matt Willsher wrote:
>
> Hi,
>
> I'm working with ansible-pull on ansible 2.0.0.2. On initial clone I get
> a failure on the first run. Subsequent runs are fine until the content of
> the git repo changes, in which case a further
Hi,
I'm working with ansible-pull on ansible 2.0.0.2. On initial clone I get a
failure on the first run. Subsequent runs are fine until the content of the
git repo changes, in which case a further error is thrown. Runs when the
repo doesn't change work ok, except for a warning about the user
Hi,
I have a role that's called from other roles via dependencies. I'm seeing
the role run twice, as discussed at
https://groups.google.com/forum/#!searchin/ansible-project/role$20dependencies$20run$20twice/ansible-project/qoC1fVKEm7I/MWDl9ALo-KoJ
I've worked around this by adding the following
Hi,
FreeBSD 10.x is missing from the support platforms metadata over on Galaxy.
Can 10 and 10.1 be added please?
Thanks,
Matt
--
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,
:
> these variables are facts -- they override inventory variables because
> they are at the same depth and are loaded later
>
>
>
>
>
>
> On Tue, Apr 29, 2014 at 10:05 AM, Matt Willsher wrote:
>
>>
>> Testing on 1.5.5 they appear at the level of "most e
based on the OS, if you really need that capability, and then could
> use group_vars/ files to do this.
>
>
>
>
> On Tue, Apr 29, 2014 at 3:05 AM, Matt Willsher wrote:
>
>> I'd like the included vars injected with the same precedence as those in
>> defaults/
ature
when it didn't exist?
>
> Sorry for confusion...
>
>
>
>
>
>
>
> On Mon, Apr 28, 2014 at 6:01 PM, Matt Willsher wrote:
>>
>> Hi,
>>
>> I'm trying to write generic roles for particular applications and keep
hitting across the s
Hi,
I'm trying to write generic roles for particular applications and keep
hitting across the same problem:
I want to set role default based on the operating system or other facts,
like include_vars, but this doesn't appear to be supported.
The only option I see practically available for templ
I have a role such:
tasks/main.yaml
---
- include: part1.yaml tags=part1
- include: part2.yaml tags=part2
tasks/part1.yaml
---
- name: "part1.1 This does stuff"
file: ...
tags: part1_1
- include: oft_used_taskset.yaml do=stuff tags=part1_2
What I was expecting is that tasks in oft_used_t