The above task is just a minimal example that shows my problem. This is actually used in my "one playbook to rule them all" and it doesn't make sense to split this playbook in multiple ones. I already know some not so nice workaround that maybe will suppress the warning.
I actually look for someone who shows me that I'm maybe missing something or telling me that this is a bug. Especially when wrapping the task in a block which still triggers the fileglob for hosts which doesn't met the when condition sounds line a bug to me. [email protected] schrieb am Dienstag, 8. März 2022 um 15:58:28 UTC+1: > On Tue, 8 Mar 2022 06:20:10 -0800 (PST) > "[email protected]" <[email protected]> wrote: > > > That's not really a solution if I have 100 playbook hosts and 5 hosts > where > > I will deploy files in this way. > > In this case, it would be more efficient to select those 5 hosts > instead of looping all 100. > > -- > Vladimir Botka > -- 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/19d46a83-2669-40d1-8823-bc8c208d447cn%40googlegroups.com.
