# Ansible 2.5 become directive and include\_tasks

**URL:** <https://forum.ansible.com/t/ansible-2-5-become-directive-and-include-tasks/27313>\
**Category:** Ansible Project\
**Created:** [April 18, 2018, 10:23am UTC](https://forum.ansible.com/t/ansible-2-5-become-directive-and-include-tasks/27313 "2018-04-18T10:23:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Petr\_Castulik](https://avatars.discourse-cdn.com/v4/letter/p/a87d85/32.png) [@Petr\_Castulik](https://forum.ansible.com/u/Petr_Castulik)\
**Post date:** [April 18, 2018, 10:23am UTC](https://forum.ansible.com/t/ansible-2-5-become-directive-and-include-tasks/27313/1 "2018-04-18T10:23:24Z")

</div>

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](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

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [April 18, 2018, 2:09pm UTC](https://forum.ansible.com/t/ansible-2-5-become-directive-and-include-tasks/27313/2 "2018-04-18T14:09:07Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Petr\_Castulik](https://avatars.discourse-cdn.com/v4/letter/p/a87d85/32.png) [@Petr\_Castulik](https://forum.ansible.com/u/Petr_Castulik)\
**Post date:** [April 18, 2018, 4:29pm UTC](https://forum.ansible.com/t/ansible-2-5-become-directive-and-include-tasks/27313/3 "2018-04-18T16:29:55Z")

</div>

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