On 02. aug. 2017 22:52, je...@soundhound.com wrote:
Sorry, I meant how you can do different plays when this is in a role's
main.yml?
I'm sorry, but I don't understand what you mean.
My bigger question is why has the lock function not been accepted into the
project. It solves a type of proble
Sorry, I meant how you can do different plays when this is in a role's
main.yml?
I have implemented assemble, but IMO it is an ugly thing when each host
generates a one line file. (first time I forgot the run_once on the
assemble.)
My bigger question is why has the lock function not been accep
On 01. aug. 2017 20:57, je...@soundhound.com wrote:
Explain to me how this works when this is the same role playbook?
I want this to be part of what is checked every time the role is run.
It would be easier to explain with some code, but I'm on vacation so I
do not have access to the code I us
Explain to me how this works when this is the same role playbook?
I want this to be part of what is checked every time the role is run.
jerry
On Tuesday, August 1, 2017 at 11:48:27 AM UTC-7, Kai Stian Olstad wrote:
>
> On 01. aug. 2017 19:42, je...@soundhound.com wrote:
> > Here's the situation
On 01. aug. 2017 19:42, je...@soundhound.com wrote:
Here's the situation I need it for:
I have my ansible machine as my dhcp server as well. When I add a new
network device, the role for the device generate a dhcp line with ansible
for zero touch provisioning. I do this by first going a set_fact
