Current Behavior
In the screenshot above, first part shows expected behavior; when pointing to an existing installation directory without any existing registrations for that tool version, fcli detects that the path contains an existing installation and shows SKIPPED_EXISTING.
However, if a registration exists for the same tool version in a different directory (as through the installation to the /tmp/test-install/2 directory), fcli fails with a non-empty target path error, instead of recognizing the existing installation and re-registering it.
Expected Behavior
The last command in the screenshot above should register the existing installation in /tmp/test-install/1 and output SKIPPED_EXISTING action instead of failing with an exception.
Steps To Reproduce
See screenshot
Environment
Anything else?
Likely closely related to #975
Current Behavior
In the screenshot above, first part shows expected behavior; when pointing to an existing installation directory without any existing registrations for that tool version, fcli detects that the path contains an existing installation and shows
SKIPPED_EXISTING.However, if a registration exists for the same tool version in a different directory (as through the installation to the
/tmp/test-install/2directory), fcli fails with a non-empty target path error, instead of recognizing the existing installation and re-registering it.Expected Behavior
The last command in the screenshot above should register the existing installation in
/tmp/test-install/1and outputSKIPPED_EXISTINGaction instead of failing with an exception.Steps To Reproduce
See screenshot
Environment
Anything else?
Likely closely related to #975