You can provide custom variables to the inventory file: [server] host1 needs_patch=yes needs_reboot=yes host2 needs_patch=yes needs_reboot=no ...
and then use this variables in the task to do each task or skip it on every server. https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html El martes, 24 de noviembre de 2020 a la(s) 14:09:51 UTC-6, [email protected] escribió: > I'm trying to automate our monthly patch process for CentOS servers. We > receive a list of servers from our Linux team each month that says which > servers need to be patched and/or rebooted. I'm wanting to have > needs_patch and needs_reboot variables attached to each host. So, each > month we would have a playbook reset all of those to false, and then using > the list from the Linux team, another playbook would set the necessary ones > to true. Then the actual patch/reboot playbook would do the work based on > the true variables and set the variables back to false upon success. I'm > having trouble determining if this is possible, and if so, what the correct > way is of doing this in the YAML. If anyone has suggestions or perhaps a > better way of achieving the same result, that would be greatly appreciated. > > Thanks! > > Chad > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1b75f420-0047-47ba-b282-e84232b1f13dn%40googlegroups.com.
