Thank you. I will certainly make sure that the collections path is defined
in ansible.cfg. And we often do run Ansible from a venv. But it is not in
this case.
I also appreciate the tips on installing ansible-core to avoid collection
bloat and setting the ANSIBLE_COLLECTIONS_PATH. Now th
Thanks for your response. I will test doing simple folder deletion in a
test environment before I try it in production.
An example of why we want to make sure that we are running a particular
version is that there have been bug fixes in a newer version of the
ansible.windows collection to fi
Hi tl,
you can also provide a YAML list.
See the documentation: it explicitly says `list / elements=string`.
https://docs.ansible.com/ansible/latest/collections/community/general/zypper_module.html#parameter-name
Providing a comma-separated string instead of a list is something
Ansible allows, b
Hi Wei-Yen and Dick
Thank you both for the fast replies. I found that multiple packages are
support as a value to 'Name', but the values must be comma-separated.
Thanks again!
tl
On Monday, September 18, 2023 at 4:28:02 PM UTC-4 Wei-Yen Tan wrote:
> It is possible. If not within the the module
I don't have a silver bullet, but to avoid surprises with collections in
multiple locations, you can hard code the collections path in your
ansible.cfg.
We use 'ansible-core' (not 'ansible') from a python venv, and when setting
that up, we install the collections in there:
ANSIBLE_COLLECTIONS_PATH
Generally, I simply do a "$ rm -rf
/home/user/.ansible/ansible_collections/" to force a collection refresh.
You can also just remove like that, the collection causing issues.
Another strategy is to force the installation, using --force, which will
remove the old version and install the new latest
