I don' t know, it feels like you are trying to force a workflow
AGAINST the base design, at that point i would suggest a) change the
workflow or b) use a different tool that actually supports that
approach
--
--
Brian Coca
--
You received this message because you are subscribed to the
On Tue, Apr 23, 2019 at 10:30 PM Brian Coca wrote:
>
> So this is a very corner case to support, not something I think we
> should do in main code, since 'single inventory' host is the
> exception, not the rule.
>
> As for running the playbook to get vars used, this might be misleading
> as the
So this is a very corner case to support, not something I think we
should do in main code, since 'single inventory' host is the
exception, not the rule.
As for running the playbook to get vars used, this might be misleading
as the vars defined and used can change dynamically per run, so it
will
Brian, thanks for the reply.
In this case, there will always be only a single item in the inventory
(a container) so I don't worry about scalability/performance right
now.
The workflow I am aiming for here is the following:
1. Write a playbook
2. Stuff container image metadata into vars
3.
No, callbacks were never intended to access ALL vars, just to receive
specific events and each one should have the proper information
associated with it. Consider that ALL vars means the full inventory,
every host and every variable associated to that host, on top of any
other variables defined in
