Install --force still does not overwrite previous installs

[ironfroggy]

Bug Report

MAZER VERSION

Running from devel

name = mazer
version = 0.5.0
config_file = /home/calvin/.ansible/mazer.yml
uname = Linux, willow-epsilon, 4.4.0-17134-Microsoft, #706-Microsoft Mon Apr 01 18:13:00 PST 2019, x86_64
executable_location = /mnt/c/Users/calvin/redhat/.virtualenvs/orion/bin/mazer
python_version = 3.7.1 (default, Oct 22 2018, 11:21:55) [GCC 8.2.0]
python_executable = /mnt/c/Users/calvin/redhat/.virtualenvs/orion/bin/python3.7

CONFIGURATION

defaults

SUMMARY

Installing with --force still bails if a previous install exists and does not force an overwrite. Adding --ignore-errors does not help, either.

STEPS TO REPRODUCE

• Install version 1.0.0 of a given collection
• Install version 2.0.0 of a given collection, with the --force flag passed to Mazer

EXPECTED RESULTS

The existing collection should be replaced

ACTUAL RESULTS

The same WARNING as without force, and the given forced version is not installed

[ironfroggy]

IMHO, it would be just as valid to remove the flag as to fix it. Its not strictly a necessary flag. You can always remove and then install a new version, instead. I would advocate for whichever is faster. The main issue now is a documented flag does not behave as documented.