"I think the feature should be available because sometimes you need to run
a task once, and then run the the playbook again, executing it by using
some new result(s) ( such as content read from a file on a remote server) "
run_once with serial now runs things once per serial batch.
If you need to
I think the feature should be available because sometimes you need to run a
task once, and then run the the playbook again, executing it by using some
new result(s) ( such as content read from a file on a remote server)
On Friday, July 25, 2014 12:30:02 PM UTC-7, Michael DeHaan wrote:
>
> It wi
It will probably just be easiest to make it an error to use run_once with
serial, because I don't want to have to pass a parameter to runner like
"run_once_has_ran" and keep an internal hash for this.
In your case, solve the problem by having another play for the "run_once"
steps outside of the ho
Yeah go ahead and open an issue for this, as it should only run once no
matter what.
Thanks!
On Fri, Jul 25, 2014 at 9:08 AM, Michael Peters
wrote:
> I'm testing out the new run_once feature and overall it's working
> great. But I then tried it in an upgrade playbook using serial. The
> task i
I'm testing out the new run_once feature and overall it's working
great. But I then tried it in an upgrade playbook using serial. The
task is no longer run just once per-play, it's run once
per-host-group. So for a serial of 2 in a target group of 10 servers
it's run once per pair, so 5 times.
Thi
