search

alertlogic / al-agents-ansible-playbooks

Ansible Playbooks to install and provision the Alert Logic Unified Agent
Apache License 2.0
10 stars 14 forks source link

Deprecation warnings with Ansible 2.4 #19

Closed szpak closed 5 years ago

szpak commented 6 years ago

Running the playbook with Ansible 2.4(.3.0) the following deprecation warnings are presented:

[DEPRECATION WARNING]: The use of 'include' for tasks has been deprecated. Use 'import_tasks' for static inclusions or 'include_tasks' for dynamic inclusions. This feature will be removed in a future release. Deprecation warnings can be 
disabled by setting deprecation_warnings=False in ansible.cfg.
[DEPRECATION WARNING]: include is kept for backwards compatibility but usage is discouraged. The module documentation details page may explain more about this rationale.. This feature will be removed in a future release. Deprecation 
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
[DEPRECATION WARNING]: win_msi is kept for backwards compatibility but usage is discouraged. The module documentation details page may explain more about this rationale.. This feature will be removed in a future release. Deprecation 
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

There is a change to have that ansible playbook not compatible with the new Ansible versions.

muram commented 5 years ago

@szpak I'm not able to reproduce this warning using v2.7.5, can you please confirm what ansible version are you using now and whether this still an issue?

szpak commented 5 years ago

@muram I'm no longer have access to any Alert Logic instance. I still see include in the code in master, so unless the Ansible team hasn't resigned from the deprecation it should still be valid.

@tomaszkiewicz Do you, by any chance, still use Alert Logic?

tomaszkiewicz commented 5 years ago

@szpak personally I do not use AL, unfortunately corporate policy doesn't allow me to tell you anything more :(

muram commented 5 years ago

Thanks @szpak and @tomaszkiewicz for the quick response, I will go ahead and close this issue as I'm not able to reproduce with the latest version of ansible. Will re-open this if someone encountered the issue again using the latest version.