Make install script work with non-privilege's environments like Azure Cloud Shell

[msfussell]

There are environments like Azure Cloud shell https://shell.azure.com/ that do not have sudo priviledges. When using the Linux install script https://v1-rc2.docs.dapr.io/getting-started/install-dapr-cli/ these fail. Currently the user has to do the following to make this work.

• wget -q https://github.com/dapr/cli/releases/download/v1.0.0-rc.3/dapr_linux_amd64.tar.gz
• chmod o+x dapr_linux_amd64.tar.gz
• tar xf dapr_linux_amd64.tar.gz
• ./dapr

The script should be able to handle non-sudo environments

The same applies to Powershell in the Azure Cloud shell. I should be able to install Dapr in Windows Powershell terminal for Azure Cloud shell

[berndverst]

@msfussell perhaps on Linux we can detect if sudo isn't present and then include an error message to instead set the DAPR_INSTALL_DIR env variable. What do you think? For example the following works in Azure Cloud Shell:

wget -q https://raw.githubusercontent.com/dapr/cli/master/install/install.sh -O - | DAPR_INSTALL_DIR="$HOME/clouddrive" /bin/bash

[berndverst]

In general the powershell script can be installed on Windows without Admin privileges.

Powershell in CloudShell does not work because the script assumes Windows File Paths, but Cloud Shell returns Linux paths.

I don't think it makes sense to support Powershell in CloudShell specifically. You can see this for yourself like this:

$script=iwr -useb https://raw.githubusercontent.com/dapr/cli/master/install/install.ps1; $block=[ScriptBlock]::Create($script); invoke-command -ScriptBlock $block -ArgumentList 1.2.0, "$HOME/clouddrive"

[berndverst]

@msfussell @AaronCrawfis @orizohar -- I think this is just a Documentation issue. What do you all thing?

[AaronCrawfis]

@msfussell @AaronCrawfis @orizohar -- I think this is just a Documentation issue. What do you all thing?

For Linux we still need to update our script to work when sudo is not present, not just when it's present but the user is not in the sudoers group.

[berndverst]

@AaronCrawfis in Cloud Shell the sudo command does not exist. When you provide DAPR_INSTALL_DIR then sudo is not being used. That's why the command above worked in cloudshell where sudo does not exist.

We could just document that as:
"If your user is not in the sudoers group or sudo is not available on your system please specify an installation directory via the DAPR_INSTALL_DIR environment variable."

Or something like that.

[AaronCrawfis]

@berndverst my preference is for it to "just work". Is there a way to update the script to auto-detect when sudo isn't present on the system and proceed as if it does exist but the user isn't in the sudoers group?

[berndverst]

@AaronCrawfis only if we install it to a different location. When sudo isn't available maybe we install to $HOME?

[AaronCrawfis]

@berndverst ah I see now the current behavior. Looks like today the script only works in non-sudo environments when an override directory is set. Only the sudo path works when no directory is specified.

My preference is to fix this so both scenarios of no sudo and not in the sudoers group are both handled by the script automatically installing it to $HOME. Thoughts?