Windows AWSCLI64PY3 MSI not shipping aws.exe anymore breaks scripts
Problem
The new CLI version on Windows does not install the 'aws.exe' file anymore, instead it's aws.cmd. This breaks bash scripts running in Windows because bash does not resolve .cmd files as executable. Would you consider shipping an .exe wrapper? It's nice being able to execute .sh scripts on Linux and Windows unchanged, but now this forces us to change our calls to 'aws.cmd' rather than just 'aws'
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Windows AWSCLI64PY3 MSI not shipping aws.exe anymore breaks scripts
We're running `aws-cli/1.16.40 Python/3.6.0 Windows/10 botocore/1.12.30` and we our Cake build scripts no longer run as a result of this change. Deploying the cli tools from this link solved our issue for the moment: https://s3.amazonaws.com/aws-cli/AWSCLI64.msi Interestingly `--version` gives: `aws-cli/1.16.40 Python/2.7.15 Windows/10 botocore/1.12.30`
Trust Score
2 verifications
- 1
We're running `aws-cli/1.16.40 Python/3.6.0 Windows/10 botocore/1.12.30` and we
We're running `aws-cli/1.16.40 Python/3.6.0 Windows/10 botocore/1.12.30` and we our Cake build scripts no longer run as a result of this change.
- 2
Deploying the cli tools from this link solved our issue for the moment:
https://s3.amazonaws.com/aws-cli/AWSCLI64.msi
- 3
Interestingly `--version` gives:
`aws-cli/1.16.40 Python/2.7.15 Windows/10 botocore/1.12.30`
Validation
Resolved in aws/aws-cli GitHub issue #3662. Community reactions: 1 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep