ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Fix --force for unversionned requirements (#23391)

Browse source 
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:
Michael Scherer 2017-04-21 13:40:47 +02:00 committed by Chris Houseknecht
parent 60de93c31d
commit 78836ec0b9
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
lib/ansible/cli/galaxy.py
View file

@ -389,8 +389,9 @@ class GalaxyCLI(CLI):
(role.name, role.install_info['version'], role.version or "unspecified")) (role.name, role.install_info['version'], role.version or "unspecified"))
continue continue
else: else:
display.display('- %s is already installed, skipping.' % str(role)) if not force:
continue display.display('- %s is already installed, skipping.' % str(role))
continue
try: try:
installed = role.install() installed = role.install()