Hi Jeff, we're going to let the tags issue slide until a dot release, due
to the complexity involved in trying to determine tags from include files.
Since includes are now dynamic and can be based on inventory variables (or
even variables set during the execution of a playbook), we have no way of
knowing for sure which files will be loaded. As a result, any tasks tagged
in those files won't be seen until the file is actually processed. We have
some ideas on how to fix this, however we don't want to hold up the 2.0
release at this time.

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

On Tue, Dec 8, 2015 at 1:07 AM, Jeff Reter <jeff.re...@gmail.com> wrote:

> https://github.com/ansible/ansible/issues/13375#issuecomment-161379814
>
> "well, in 2.0 missing tags will not error out (yet), but this does seem
> like an interesting corner case, it should affect empty plays and includes
> also."
>
>
>
> Am Montag, 7. Dezember 2015 19:31:31 UTC+1 schrieb James Cammarata:
>>
>> Hi all, we're happy to announce the second release candidate for Ansible
>> 2.0!
>>
>> This release candidate includes a few bug fixes and cleanups since rc1
>> was released, and if we don't have anything major show up in the next few
>> days we'll be releasing 2.0-final, so get testing!
>>
>> For details and background, please see the original beta announcement
>> here:
>> https://groups.google.com/d/msg/ansible-project/_hTjEIpbA_Y/GtllImCkCQAJ
>>
>> How do you get it?
>> ----------------------------------------------------------------------
>>
>> The tar.gz of the release can be found here:
>>
>> http://releases.ansible.com/ansible/ansible-2.0.0-0.7.rc2.tar.gz
>> SHA256: 4f7227260becd444435bc4eddac21c603a725c52eddebff19a2a6708dbbe1462
>>
>> You can also test against the git repository as follows:
>>
>> $ git clone https://github.com/ansible/ansible.git
>> $ cd ansible
>> $ git checkout v2.0.0-0.7.rc2
>> $ git submodule update --init
>>
>> You can then source our testing script:
>>
>> $ . hacking/env-setup
>>
>> or you can build your own .tar.gz (output will be
>> dist/ansible-2.0.0.tar.gz):
>>
>> $ make sdist
>>
>> If you discover any errors, or if you see any regressions from playbooks
>> which work on 1.9.x and prior, please open a Github issue and be sure to
>> mention you're testing against this release candidate.
>>
>> Thanks!
>>
>> James Cammarata
>> Director, Ansible Core Engineering
>> github: jimi-c
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-devel+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAMFyvFgSu2eeo_ehXc8UZbU%2BsycH7w6TvrZHMwJrUb1%2B-i9OuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to