If you don't mind making a tarball with the roles, you can use
https://github.com/javiplx/ansible-library/, which is basically a install
only private galaxy server, from where you can serve your packaged roles
(so, it doesn't matter the tree where they live).
Javier Palacios
On Fri, Ma
ve the issue that, as they are in private repositories, I need to arrange
permission to clone/download.
Javier Palacios
--
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 i
which I've just submitted
as pull requests.
Javier Palacios
--
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 ansible-project+unsubscr...@googl
With the setup you describe, you have basically two jenkins-aware options.
One, which is closer to what you are currently making, is to give ssh
permission from jenkins to ansible servers. In that case you will need also
one of the plugins that allows Jenkins to execute ssh commands in a
different
Not used 1.7, only 1.9. And my experience is that only variables defined on
defaults/main.yml on dependant role can be overridden. I usually use
group_vars to override them, but in a few corner cases the only way I found
to achieve what you pretend to do is to override them at the playbook
level, a
r example,
accept an unknown ssh key) will stop the playbook. So I believe that one of
the the ´async´ functionalities missing is handling playbook questions.
If the use of nohup is just to capture both stdout & stderr, there are
other ways to do it.
Javier Palacios
--
You received this me
If you are using 1.9, there is a "exclusive" parameter that I believe makes
exactly what you want, although it will force you into some extra work if
you want multiple allowed keys
Javier Palacios
On Wed, Oct 21, 2015 at 12:20 PM, DrDth wrote:
> Hello Ansible Community,
>
&g
Hello Josef,
you might have a look to the augeas role. I've not used it with ansible but
with puppet, and if you are changing a standard configuration file is
probably the best approach. Even if you don't want to use the role, use
augeas with a 'command' might also help
Jav
names and some EC2 tags that we define.
Javier Palacios
--
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 ansible-project+unsubscr...@googlegroups
o be defined with a
variable, either in the way commented by John which or with a similar
approach.
Javier Palacios
--
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
Its maybe an issue with the expression I did use `where the inventory
lives` means under the same directory where is your inventory. So, it looks
for roles on /path/to/playbok/roles and then on /path/to/inventory/roles.
Javier Palacios
On Mon, Aug 31, 2015 at 11:24 PM, Greg DeKoenigsberg
wrote
le you are testing is None, the default will
not be used.
Javier Palacios
On Tue, Sep 1, 2015 at 1:55 PM, Paul Tötterman
wrote:
> Sorry to resurrect this old thread.
>
>
>> ansible_eth1["ipv4"]["address"] | default("127.0.0.1")
>>
>
> I tr
book lives (this one rules). So you can keep your standard
roles along the inventory and the higher version ones along the playbooks
where they are used. It might not suit your needs, and it will potentially
end in as many directories as playbooks you have, but might help.
Javier Palacios
--
You re
13 matches
Mail list logo
