On 10. okt. 2017 18:20, Patrik Ragnarsson wrote:
On Tuesday, September 19, 2017 at 7:20:02 AM UTC+2, Toshio Kuratomi wrote:Hi all, On behalf of the entire Ansible open source community, we are very happy to announce that Ansible 2.4.0 has been released! This release includes many new features and improvements, including the following: * New import/include keywords to replace the old bare `include` directive: - Using `import_*` (`import_playbook`, `import_tasks`, `import_role`) directives are static. - Using `include_*` (`include_tasks`, `include_role`) directives are dynamic. - For more information, see http://docs.ansible.com/ansible/latest/playbooks_reuse_includes.htmlIsn't it pretty aggressive to deprecate the use of 'include' in the same version that introduces the replacements?
Deprecate doesn't mean removed, it's a message to inform the user that it will be removed in the future (two major version after marked as deprecated).
Also, the docs says the following about 'import_tasks' and 'include_tasks' making it an even more of aggressive move: "This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface."
include in 2.3 was also flagged as preview https://docs.ansible.com/ansible/2.3/include_module.html -- Kai Stian Olstad -- 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/59cc6ff7-4bb0-447a-c52b-0876cf566138%40olstad.com. For more options, visit https://groups.google.com/d/optout.
