You can already do:
- action: {{ ansible_pkg_mgr }} name=some-pkg-name
On Sunday, June 7, 2015, Michael Johnson there...@gmail.com wrote:
It has always sort of bothered me that ansible does not have a generic
'package' module that you then can tell it what 'provider' to use if you
want to
Hmm So, use rsync to push the scripts to each server, making sure to
only send the data relevant to each specific server. Right?
Um, isn't that basically what Ansible does by default? It pulls together
the relevant information for each server, then transfers the scripts to
that server, and
I tried with a when statement on the handler definition (with a variable
defined by me) but id didn't seem to work either, the handler is executed
anyway, and the AMI creation fails for that.
El sábado, 6 de junio de 2015, 12:14:50 (UTC+2), Dan C escribió:
I would like the same feature.
I
try creating a group_vars/windows and put the settings in there, then
make sure the windows machines belong to the 'windows' group.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
Ansible Project group.
To unsubscribe from this group and stop
handlers are not affected by tags in general, but they should be
affected by when:
--
Brian Coca
--
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
I have the same issue, and I didn't manage to solve it.
here is an example from my playbook:
- name: add newly provisioned servers to a group linux_dsm
local_action: add_host hostname={{item.private_ip}} groupname=xxx
ec2_tag_Group=xxx
with_items: ec2_linux_dsm.instances
I have the
Hi Group,
Wonder if someone have a feedback on the following issue:
I'm creating two machine in EC2 - One is Windows and the other is Linux.
Once VMs are up and running I run a test on Windows which take like 1 hour,
and if run successfully I move on to Linux
and run anther test. Total time of
Got it, this makes perfect sense. Always nice to have the background on
inconsistencies like this (for me a least it removed a mental block). With
this background coupled with the notion of using 'action', perhaps
'service' could be deprecated and eventually removed in favor of different
Yes, it is a contradiction, sadly it is very hard to remove 'service'
now, it is a huge pathway of detection and fallbacks and I would be
very happy to create a systemd, upstart, initd and other modules to
substitute it.
You just have to look at the tickets to see that every time we do a
minor
Once you have this kind of restrictive environment, you might want to
look into Tower, it will pull/push provision servers on request and
keeps things pretty tight and secure. It also has audit trails and
reports which tend to be needed when security is at this level.
--
Brian Coca
--
You
On Thursday, 4 June 2015 22:34:33 UTC+2, David Reagan wrote:
Hi David,
We had the same issue, where we didn't like our entire git repository
exposed on all servers while using ansible-pull.
We have solved our problem differently. Instead of letting ansible-pull do
a git checkout, we have a
11 matches
Mail list logo