mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
Fix --force for unversionned requirements (#23391)
In current stable (2.2), ansible galaxy install --force do erase a role, even if the version is not set. This commit should restore that specific behavior, in accordance to people reports: https://github.com/ansible/ansible/issues/11266#issuecomment-273801480 It was also the behavior planned in the initial discussion: "if you're not fixing versions in your roles file, then it's fine to expect that the role will be reinstalled each time you run ansible-galaxy install.", cf https://github.com/ansible/ansible/pull/12904
This commit is contained in:
parent
60de93c31d
commit
78836ec0b9
1 changed files with 3 additions and 2 deletions
|
@ -389,6 +389,7 @@ class GalaxyCLI(CLI):
|
|||
(role.name, role.install_info['version'], role.version or "unspecified"))
|
||||
continue
|
||||
else:
|
||||
if not force:
|
||||
display.display('- %s is already installed, skipping.' % str(role))
|
||||
continue
|
||||
|
||||
|
|
Loading…
Reference in a new issue