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

chore(middleware-sdk-s3): update s3 status 200 error handling #6232

Merged
merged 3 commits into from
Jul 17, 2024

Conversation

kuhe
Copy link
Contributor

@kuhe kuhe commented Jun 27, 2024

Issue

internal

Depends on #6279 being merged

Description

Updates the s3 status 200 error behavior. For JSv3 middleware, the change is to ignore the <Error> tag within a 200 response if it is not the top level XML element.

For Command criteria, it is no longer an allowlist, rather any operation that does not have a response payload of type blob with streaming trait.

Testing

Added unit test.

  • e2e
  • integ

@kuhe kuhe requested a review from a team as a code owner June 27, 2024 15:47
@kuhe kuhe force-pushed the chore/s3-200-error branch 5 times, most recently from b7585ac to 140913b Compare June 27, 2024 17:24
@kuhe
Copy link
Contributor Author

kuhe commented Jul 15, 2024

updated to require smithy-lang/smithy-typescript#1336

uses stream splitting instead of turning the stream into a bytearray, which is incompatible for event streams

@kuhe kuhe force-pushed the chore/s3-200-error branch 4 times, most recently from 7a04eaa to 1a8882b Compare July 16, 2024 20:41
@kuhe
Copy link
Contributor Author

kuhe commented Jul 17, 2024

  • tested in browser app

@kuhe kuhe merged commit 9119ae6 into aws:main Jul 17, 2024
5 checks passed
@kuhe kuhe deleted the chore/s3-200-error branch July 17, 2024 15:32
Copy link

github-actions bot commented Aug 1, 2024

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants