On Tue, Mar 15, 2016 at 4:37 AM, Strahinja Kustudić <[email protected]> wrote:
> On Tue, Mar 15, 2016 at 7:12 AM, James Cammarata <[email protected]> > wrote: > >> Because we do not load the included file until we reach that point in the >> execution, we no longer know anything about the tasks contained within that >> file. This means that we don't know about tags on those tasks, and >> notifying handlers within those files do not work either (which breaks a >> common use case for many people). >> > > Your reply basically sums up my answer above. Include was broken with 2.0 > for a common use case for many people and now you would like to fix it by > making all those people change their playbooks for it to work as they > expected it to work in the first place, because of an uncommon use case > which didn't even work in older versions. > No, the entire point of the config options is to allow users to switch to 2.0 without having to change their playbooks when moving from 1.x. Include loops were not an uncommon use-case, in the 1.5 years or so since we removed the capability, that was one of the most often requested features, which is why we implemented dynamic includes in 2.0 (to make them actually work like people expected). -- 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/CAMFyvFizYLJW58vEZXN6BmsgdhhCdFJL2cdo6KGnf83bskxiRA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
