+1 I'm also interested in this issue, as tagging includes is a core practice in my workflow.
On Sun, Nov 8, 2015 at 4:17 AM, Michel Blanc <[email protected]> wrote: > Hi all, > > Playing with 2.0, I just stumbled on: > > [DEPRECATION WARNING]: You should not specify tags in the include > parameters. All tags should be specified using the task-level option. > This feature will be removed in a future release. > > > So, basically, this means that you cannot do this anymore: > > > myrole/tasks/main.yml: > > - include: setup.yml tags=myrole,setup > - include: myrole.yml tags=myrole > > > This pattern is very handy: it lets you "assign" tags on all tasks in a > file. This helps keeping tasks descriptions less verbose, and improves > readability > > If I understand the warning correctly, we won't be able to do that in > the future. What is the rationale behind the decision ? Will there be an > alternate way to do it (besides blocks) ? > > Thanks, > > M > -- > Michel Blanc > { :github => "@leucos", :twitter => "@b9m", :gpg => "0X24B35C22" } > > -- > 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/563EE8FD.4080105%40mbnet.fr. > For more options, visit https://groups.google.com/d/optout. -- Ivan Sichmann Freitas -- 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/CAG2tFJwn%2Ba7bMJFFJSP4veHYoLw4teZUj8J_3hEQMTT-dbqrSg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
