aws s3api wait bucket-not-exists does not handle success case #1111
Comments
|
With this PR now merged: #1220 Issue is now fixed. Closing. |
thoward-godaddy
pushed a commit
to thoward-godaddy/aws-cli
that referenced
this issue
Feb 12, 2022
* chore(version): set 0.14.3.dev1 version (aws#1112) (aws#1113) * Depend on development version of lambda-builders for dev builds (aws#1111) * Depend on development version of lambda-builders for dev builds * Adding prod.txt to manifest * Splitting dev and tool dependencies * fix(build): Resolve path after .aws-sam is created (aws#1110) * fix(build): Resolve path after .aws-sam is created * fix: build (make pr) * Design and implementation for producing debug build artifacts (aws#1095) * design: Initial Design for producing debug artifacts * initial implementation * Adding unit tests * Integration test with debug build mode * Adjust Design doc and add keyword arg to a call * fix(dotnet): init template fixes (aws#1117) * chore(version): set 0.15.0 (aws#1125) * Revert "Depend on development version of lambda-builders for dev builds (aws#1111)" (aws#1128) This reverts commit 7e9de790e23791ba176faff2030286db4007e503. * Bumping to Lambda Builders 0.3.0 (aws#1129) Bumping to Lambda Builders 0.3.0 * fix(func-tests): add dependency manager param (aws#1130)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given a bucket that does not exist:
when we try to wait for that bucket to not exist, I'd expect the command to return immediately but instead we get an error:
This should go away with the switchover to clients, but in the meantime this happens because we can't parse an error code out of the head object response because it does not have a response body to parse.
The text was updated successfully, but these errors were encountered: