Update - here's what I've tried so far. It runs successfully, but the
facts don't persist after the playbook is done. I want them to persist so
that we can re-run the patch job as needed until all of them are successful
without manually going and selecting hosts.
- hosts: "{{ env|default('all') }}"
gather_facts: no
become: no
tasks:
- set_fact:
needs_patch: False
needs_reboot: False
cacheable: yes
On Tuesday, November 24, 2020 at 2:09:51 PM UTC-6 Chad Campbell wrote:
> 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/daa73496-e3b3-4adb-84d2-1e55902ee561n%40googlegroups.com.
