issue on running cloudypad cli

[dchhouen]

I ran the curl command to install curl -fsSL https://raw.githubusercontent.com/PierreBeucher/cloudypad/master/install.sh | sh , but i do not see any values after running cloudypad create or cloudypad -v

It seems like the install.sh ran fine.

See below images.

[dchhouen]

i am running Linux Mint 21

[PierreBeucher]

Can you try to run

cloudypad create -v 0

(will run with high verbosity)

I'll try to run a VM with Linux Mint to reproduce, thanks for these details

[PierreBeucher]

Should be fixed by #14

To explain a bit: Cloudy Pad creates a Docker image on-the-fly to run the CLI (this is temporary for MVP while i'm working on a better system), for this we need to ensure your local user matches the one in the container to avoid permission issues. This failed because I mistakenly used username instead of user ID at some place in the script.

Normally you should have a got a nice error message, but another failsafe mechanism (bash -e flag) prevented that.

Should be better now :) Do not hesitate if you have other issue, Cloudy Pad is still pretty new and experimental and there may be bugs like this. I'll make myself available to fix them ASAP.

[dchhouen]

Tried to reinstall with the new update but it looks like I'm still having an issue .

steps ran

rm -rf ~/.cloudypad
curl -fsSL https://raw.githubusercontent.com/PierreBeucher/cloudypad/master/install.sh | sh
closed terminal and re-opened new terminal
cloudypad create -v 0 # no output was seen .

[PierreBeucher]

🤦 I didn't make a new release so the fix wasn't available sorry. Incoming.

[PierreBeucher]

New release done. Can you try again? If you encounter another issue, open script at ~/.cloudypad/bin/cloudypad and append set -x right after #!/usr/bin/env bash such as:

#!/usr/bin/env bash

set -x

To get more debug information.

[dchhouen]

perfect, i'm able to get it running. appreciate you providing a fix so quickly. this is a really neat wrapper for multi-tools

Separate question:
For credentials on aws, is it retrieving it from reading a file or pulling from the current terminal session? It seems like it is doing some variant of the former. I did an env override in the current terminal session for aws creds , but it look like it just used the default credentials configurations.

[PierreBeucher]

Great ! Thanks for your encouragements, such feedbacks are greatly appreciated :)

In short, (almost) everything runs in a container. For AWS ~/.aws is available in container via bind mount, but currently host env variables such as AWS_* are not passed into container. I'm working on this via d4ee54c on #18 to allow for simple use case like using a profile (AWS_PROFILE) or directly using credentials via AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. Though some use cases may not be possible yet (like having AWS creds in non-standard location) it should be a good starting point.