CLI installer is broken by 2.49.0 release

[gwjo]

The CLI based installer via curl is broken if it requires sudo access.

$ curl -fL https://install-cli.jfrog.io/ | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2510  100  2510    0     0  23320      0 --:--:-- --:--:-- --:--:-- 23457
Downloading the latest version of JFrog CLI...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 25.5M  100 25.5M    0     0  45.0M      0 --:--:-- --:--:-- --:--:-- 45.0M
mv: cannot create regular file '/usr/local/bin/jf': Permission denied
We'd like to install the JFrog CLI executable in /usr/local/bin. Please approve this installation by entering your password.
mv: invalid option -- 'e'
Try 'mv --help' for more information.
mv: cannot create regular file '/usr/bin/jf': Permission denied
We'd like to install the JFrog CLI executable in /usr/bin. Please approve this installation by entering your password.
mv: invalid option -- 'e'
Try 'mv --help' for more information.
could not find supported destination path in $PATH

This is caused by the line below:

jfrog-cli/build/installcli/jf.sh

Lines 77 to 79 in a559d32

	echo ""
	echo "We'd like to install the JFrog CLI executable in $1. Please approve this installation by entering your password."
	if sudo mv $FILE_NAME "$1" -eq "0"

The if statement should be:

       if sudo mv $FILE_NAME "$1"

[akire0ne]

Same here

[alexiaizenberg]

Ditto

[gavinclarkeuk]

Can install it like this:

curl -fL https://releases.jfrog.io/artifactory/jfrog-cli/v2-jf/2.48.0/scripts/install-cli.sh | sh

[yahavi]

@gwjo @gavinclarkeuk @alexiaizenberg @akire0ne
Thanks for flagging this problem. We apologize for the inconvenience. We're currently in the process of preparing a speedy fix, which you can track here: #2240. We'll be sure to keep you updated on our progress.

[yahavi]

@gwjo @gavinclarkeuk @alexiaizenberg @akire0ne
Version 2.49.1 with the fix is out now. Feel free to share your thoughts and feedback on it.