This seems fine to me, +1
On Thu, Feb 13, 2014 at 4:26 PM, Bruce Pennypacker
bruce.pennypac...@gmail.com wrote:
I occasionally run into an issue with the ec2_elb module that I think
needs to be addressed. This module is used to add and remove Amazon EC2
instances to/from an Amazon load
I'll make a resubmit with the changes ... but the font is going to be
yellow!
--
Brian Coca
Stultorum infinitus est numerus
0111011100100110010101101110001001110111011000010110011101010010011100110110110101110111001001110111
Pedo mellon a minno
--
You
I changed the settings, but kept the trinary boolean (I know it bugs you)
as I think it is the simplest implementation.
--
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
Is there any way to run a command after the playbook has finished running,
so it would run once no matter how many hosts were processed? Kind of a
callback handler or super-notifier.
I have a Hipchat message generated after deploying and I'd rather see one
summary message than a line for each
We'll take a look.
It's probably better if we can get this to have predicate methods like
play.should_gather_facts() or something if we want to escape the need
for having to repeat test-logic for it in the code every time this field is
accessed. But that can wait.
On Sat, Mar 15, 2014 at 6:15
I actually have a pull request submitted to supply a hipchat callback plugin:
https://github.com/ansible/ansible/pull/6376
The callback method of significance is `playbook_on_stats`
This is the callback method I use to send a hipchat notification that provides
statistics about results at the
you can also have a task or play at the end of your playbook that uses the
existing hipchat notification module.
your current playbook
- hosts: localhost
tasks:
- hipchat:
--
Brian Coca
Stultorum infinitus est numerus
I wonder if there is an elegant way to have a few tasks in a handler file,
and execute them either triggered by other tasks or forced based on an
input parameter.
Here is the scenario I have in mind..
1) use ansible to sync a git repo, if that repo is updated, trigger a build
handler
2)
I wonder if there is a way to report changed for a group of tasks..
For example, I want to have a play like this:
- include: sub-play1.yml
- include: sub-play2.yml
only when something changed in sub-play1
Or, a play like this:
- hosts: group1
tasks:
- t1
- t2
- hosts: group2
