aws / aws/aws-elastic-beanstalk-cli-setup
On windows eb cannot be placed in a directory with spaces
- Dominant language
- Python
- Stars
- 537
- Forks
- 226
- PR merge metrics
- No merged PRs in 30d
Description
**1. Please specify the following:**
- OS: Windows
- Shell (Bash, PowerShell, Zsh, etc.): Powershell
- [X ] **I have reviewed the troubleshooting tips described [here]() and they do not solve my problem**
**2. Description**
After installation a eb.ps1 file ends up in C:\Users\ because on windows usernames can contain spaces and some long gone sysadmin thought that was actually a good idea I ended up with a space in my username at my workplace.
Anyway by modifying eb.ps1 it now works:
```
c:\Users\A9DA8~1.BRU\.ebcli-virtual-env\Scripts\activate.ps1
c:\Users\A9DA8~1.BRU\.ebcli-virtual-env\Scripts\eb $args
deactivate
```
As you can see I used the old dos shortname instead of the generated long name which is causing problems:
```
c:\Users\My Name\.ebcli-virtual-env\Scripts\activate.ps1
c:\Users\My Name\.ebcli-virtual-env\Scripts\eb $args
deactivate
```
Contributor guide
Research direction
Start by locating the code that generates eb.ps1 and the installer path for .ebcli-virtual-env. Reproduce the installation on Windows PowerShell with a username containing spaces, then verify the generated script runs without manual edits and still activates, invokes eb, and deactivates the environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, python
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100