I also agree it would have made more sense if the dynamic include was optional and the default behavior was the version 1 way. But I also see how this is hard to justify now that Ansible 2 works as it does, it's hard to go back. If Ansible follows semver that would actually mean we have Ansible 3 knocking on our door if the behavior is switched back.
Ideally, in my opinion, the new functionality would have been added with a different name, for example "import" instead of "include". This would have allowed a clean way to migrate without breaking things. It also makes it possible to distinguish between two complete different features by name. We have adopted Ansible 2 but I would not mind if the behavior changed back to the old static include. In any case, I will adjust our roles. Most of the includes do not need to be dynamic and I would set them to static just to get rid of the hundreds blue include statements during playtime. Now, I'm wondering what happens if a static include includes a file which has a dynamic include. :) Am Dienstag, 15. März 2016 09:37:46 UTC+1 schrieb Strahinja Kustudić: > > On Tue, Mar 15, 2016 at 7:12 AM, James Cammarata <[email protected] > <javascript:>> 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. > -- 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/a0cd9f0a-d5ee-4758-9fbb-6da25ac062c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
