Ansible 2.5 become directive and include_tasks

Archives Ansible Project
1

Hello,

I have a question concerning the become directive and include_tasks. After Ansible upgrade to 2.5 the become directive is not escalated to included tasks.

I’m aware of https://docs.ansible.com/ansible/2.5/porting_guides/porting_guide_2.5.html#dynamic-includes-and-attribute-inheritance, especially:

All attributes applied to a dynamic include_* would only apply to the include itself, while attributes applied to a static import_* would be inherited by the tasks within.

Hence my question is whether “attributes” word involves also the become directive(s) or it is a bug?

This new behaviour makes upgrade much harder than expected and become for include_tasks itself doesn’t make a sense.

Thank you
Petr

`
$ ansible --version
ansible 2.5.0
python version = 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609]

$ cat whoami-playbook.yml

2

become is also an attribute. This is the expected behavior in 2.5

3

Hello Matt, thank you for the confirmation. Best regards, Petr