Skip to content

Conversation

syall
Copy link
Contributor

@syall syall commented Dec 13, 2023

Issue

Issue number, if available, prefixed with "#"

N/A.

Description

What does this implement/fix? Explain your changes.

Add event streaming input integrations relative to auth.

  • feat(experimentalIdentityAndAuth): remove AddEventStreamHandlingDependency experimental branch
  • feat(experimentalIdentityAndAuth): add order for AddWebsocketPlugin

Testing

How was this change tested?

See the diff in this branch: https://github.com/syall/aws-sdk-js-v3/tree/TEMP-streaming

The following clients (services with event stream inputs) compile correctly:

  • client-lex-runtime-v2
  • client-rekognitionstreaming
  • client-transcribe-streaming
yarn generate-clients -n -g \
codegen/sdk-codegen/aws-models/lex-runtime-v2.json \
codegen/sdk-codegen/aws-models/rekognitionstreaming.json \
codegen/sdk-codegen/aws-models/transcribe-streaming.json \

Additional context

Add any other context about the PR here.

N/A.

Checklist

  • If you wrote E2E tests, are they resilient to concurrent I/O?
  • If adding new public functions, did you add the @public tag and enable doc generation on the package?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@syall syall changed the title feat(experimentalIdentityAndAuth): add relative order for streaming integrations' feat(experimentalIdentityAndAuth): add event streaming input integrations relative to auth Dec 13, 2023
@syall syall marked this pull request as ready for review December 13, 2023 18:25
@syall syall requested a review from a team as a code owner December 13, 2023 18:25
@syall syall merged commit a12b2eb into aws:main Dec 13, 2023
@syall syall deleted the ts-ia-streaming-codegen-ordering branch December 13, 2023 18:39
Copy link

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 Dec 28, 2023
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.

2 participants