Thanks. Personally I think I'd shy away from coupling this relationship in the inventory but instead use groups and enforce the order by having multiple plays in a given playbook (something like the following), but whatever works for you.
# reboot_stuff_playbook.yml - NOT tested, just to illustrate idea -- hosts: domain_controllers tasks: - win_updates - win_reboot hosts: db_servers tasks: - win_updates - win_reboot hosts: app_servers tasks: - win_updates - win_reboot Jon On Tuesday, May 24, 2016 at 11:50:13 AM UTC+1, Mike Fennemore wrote: > > Hi Jon, > > We do currently use a dynamic inventory. Basically with the Windows domain > servers we have instances where an application server would depend on a > database server that would rely on a domain controller. In that example we > would want a certain order of update and reboot. > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/e9f457b5-371c-4472-951d-a046a24ae312%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
