Michael Scherer 78836ec0b9 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		2017-04-21 07:40:47 -04:00
..
__init__.py	Add ansible executable path (argv[0]) to --version (#22262)	2017-04-03 14:01:59 -04:00
adhoc.py	removed bad ignore as host can override connection	2017-03-28 11:32:22 -04:00
console.py	.--. . .--. ---.. / .. ... / .- -. -. --- -.-- .. -. --.	2017-03-24 15:52:36 -04:00
doc.py	added docs to CLI docstringsadded	2017-03-24 15:52:36 -04:00
galaxy.py	Fix --force for unversionned requirements (#23391)	2017-04-21 07:40:47 -04:00
playbook.py	added docs to CLI docstringsadded	2017-03-24 15:52:36 -04:00
pull.py	.--. . .--. ---.. / .. ... / .- -. -. --- -.-- .. -. --.	2017-03-24 15:52:36 -04:00
vault.py	Update vault.py	2017-03-24 15:52:36 -04:00