command/shell module warn deprecation

Archives Ansible Project
1

Good Morning,
I manage the building of some virtual machine templates using packer. I am leveraging ansible as part of this, and when I am doing some cleanup after the setup is done to prepare for the conversion to template, and a couple of the options I need in yum/dnf, etc don’t exist in the module don’t exist. So, to get around this, I am using the command module, but I get a warning that I should use the module, but that if I am doing it for a specific reason, I should use warn: false or set the option to ignore warnings in my ansible.cfg. Since I am using a “ansible_local” provisioner in packer, I don’t use an ansible.cfg, so I was wondering if there is another way to accomplish the warn: false option since it has been removed in the more recent versions of ansible.

–John

2

I think you can place an ansible.cfg file in the folder where your ansible is running. We do this for our packer image management service that also uses ansible in the provisioner stage.

Walter

3

yeah, I saw that, and I might go down that road, but wanted to see if there was a better way first.

–jp