awscli-local icon indicating copy to clipboard operation
awscli-local copied to clipboard

💲 "awslocal" - Thin wrapper around the "aws" command line interface for use with LocalStack

Results 13 awscli-local issues
Sort by recently updated
recently updated
newest added

I tried to use `awslocal` with aws-cli installed by [asdf](https://asdf-vm.com/) but could not. The reason is that `asdf` uses `HOME` env variable. https://github.com/asdf-vm/asdf/blob/b7dd291c983af321af20550fa89bf1cfbc888aec/asdf.sh#L26 Please pass `HOME` env variable.

If you are using awslocal s3api to create bucket its not wrapping the endpoint for LocalStack you need to add the endpoint self. ``` bash awslocal s3api create-bucket \ --bucket...

cannot-reproduce
should-be-fixed
awaiting-response

```sh $ LOCALSTACK_HOST='localhost:4599' awslocal s3 ls 0 Port could not be cast to integer value as '4599:4566' ```

### Specs OS: ManjaroLinux Version: 21.2.6 PythonVersion: 3.7.4 PipVersion: 22.1 ### Description I tried installing the `awscli-local` package using pip, but I get the following output: ``` Collecting awscli-local[ver1] Using...

Your 0.15 release crashes my docker and my buildkit container. **Source: It contains a fork bomb / memory leak** **Using the previous version (0.14) fixes the issue.** In my tests,...

bug
needs-triaging

Hi everyone ! I tried to install awscli-local with ebcli v3 but : - awslocal requires six, which requires botocore >= 1.20.0 - latest ebcli (3.19.3) requires botocore < 1.20...

Trying to add read-timeout to my awslocal command but it doesn't help: _awslocal sqs list-queues --cli-read-timeout 5_ connect timeout doesn't work as well: _awslocal sqs list-queues --cli-connect-timeout 5_ **OS: Windows...

Following #59, pass HOME env variable to ENV_VARS_TO_PASS.

Adds a basic GitHub action regression test to verify that basic awslocal commands are still working. Can be extended with multiple other cases as well like: - More `awslocal ...`...

With the recent release of AWS CLI (v1.29.0 and v2.13.0), the environment variable `AWS_ENDPOINT_URL` is now being referenced by the aws commands as well. This release has caused a bug...