AWS CLI one line installer failing when the path to it contains a space (e.g. WSL)
Describe the bug
Hello,
I was attempting to install AWS CLI on WSL (Windows Subsystem for Linux, Debian). The one-liner worked nice until it broke because it couldn't find the installer, and this is the error I got: ./aws/install: 78: /mnt/c/Users/MyFirstName: not found
This was weird, but it made sense since I was installing AWS CLI from `/mnt/c/Users/MyFirstName\ MyLastName' (which is how WSL references the host's file (Windows files).
I'm not sure if that intended behavior, but it looked to me like it was an error case that should be handled, so I thought it might be better to report it anyway.
Regression Issue
- [ ] Select this option if this issue appears to be a regression.
Expected Behavior
The install succeeds regardless of whether the path contains spaces.
Current Behavior
The install stops midway.
Reproduction Steps
Put the installer on a path that contains spaces, attempt to install AWS CLI.
Possible Solution
Haven't looked at the code unfortunately, but perhaps better to check the path properly at the beginning.
Additional Information/Context
No response
CLI version used
aws-cli/2.19.1 Python/3.12.6
Environment details (OS name and version, etc.)
Linux/5.15.153.1-microsoft-standard-WSL2 exe/x86_64.debian.12
Hi @aneutron, thanks for reaching out. I was not able to reproduce the same issue. I was able to install AWS CLI on a file path containing a space. Were you able to reproduce this on a non-WSL environment? If so, could you go into detail about your steps to do that? Thanks!
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.
Hey ! Sorry I missed your answer. I'll try and get you detailed reproduction steps and possibly a fix in the next few days.
any update on this?
Hello aneutron, is this still an issue? and is there a repro of issue for this?
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.