This is an interesting post that touches upon the topic: https://medium.com/opsops/ansible-2-5-delegate-to-and-include-role-20cd7e67008e
The way I look at it, Ansible team has chosen a path of keeping the product competitive vs. maintaining backward compatibility at all costs. The Best Practices recommend avoiding Tags all together, as well as other traditional features that are static in nature and aren't considered in dynamic Includes. This (supposedly) allows writing better playbooks. Yes, there is a potentially considerable effort re-writing old ones that don't comply with the new model. On the other hand, with the speed of the industry changes, since the time the old books were written, an average team would probably switch to another tool or technology all together as part of the cycle, so keeping Ansible as a valuable option for future cycles pretty much means that the archaic way the old playbooks were written in has to change. On Friday, August 24, 2018 at 11:17:27 PM UTC+8, Frank Thommen wrote: > > Thanks a lot Kai, > > > -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/977ed0f9-45ee-4985-894b-4618d04173c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
