Ansible Galaxy Core 2.15.3 changed behavior of identifying installed collections

[0xFelix]

With the version bump to 2.15.3 the behavior of ansible-galaxy identifying installed collections changed. [1]

This leads to ansible-galaxy picking up an already installed collection, when trying to install it into a different specified path. [2]

The ansible-galaxy install commands in [3, 4] likely need a --force switch to override that behavior?

[1] https://github.com/ansible/ansible/blob/v2.15.3/changelogs/CHANGELOG-v2.15.rst#id14
[2] https://github.com/kubevirt/kubevirt.core/actions/runs/5887415388/job/15966833282#step:8:283
[3]

github_actions/.github/actions/build_install_collection/action.yml

Line 86 in d74ea0a

- name: Install collection and dependencies (with --pre flag)

[4]

github_actions/.github/actions/build_install_collection/action.yml

Line 92 in d74ea0a

- name: Install collection and dependencies (without --pre flag)