Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

s3 ls returns incorrect return codes #866

Closed
doapp-ryanp opened this issue Aug 6, 2014 · 0 comments · Fixed by #1008
Closed

s3 ls returns incorrect return codes #866

doapp-ryanp opened this issue Aug 6, 2014 · 0 comments · Fixed by #1008
Assignees
Labels
bug This issue is a bug. s3

Comments

@doapp-ryanp
Copy link

s3 ls of an object (on a valid bucket) that does not exist returns a 0 return code.

> aws --profile myprofile s3 ls s3://mybucket/dne.txt
> echo $?
0
@kyleknap kyleknap added the s3 label Aug 7, 2014
@kyleknap kyleknap self-assigned this Nov 17, 2014
thoward-godaddy pushed a commit to thoward-godaddy/aws-cli that referenced this issue Feb 12, 2022
* Add Ruby to Supported Runtime Enum

* Ruby Project Template Changes

WIP: Unit tests may have a notion of a central Gemfile that isn't
compatible with per-function Gemfile pattern that `sam build` expects.

* Tweaks

Global Gemfile for tests. Gemfile in the function for use in tests.

Hat tip to lauratpa and her PR aws#860 which is the core of this part of
the change set.

* Ruby Init App in Working State

* fix: add integration tests for sam build - ruby

* bump: version bump aws-lambda-builders to 0.0.5

* fix: requests version pin and imports

* fix: string paths on Pathlib for py2

* fix: README - add references to build
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. s3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants