Add generated Lex Runtime V2 client with integration tests by Alan4506 · Pull Request #51 · awslabs/aws-sdk-python

Alan4506 · 2026-04-03T19:31:45Z

Description of changes:

This PR adds support for the Lex Runtime V2 service by adding the latest Smithy model and code-generating a new client package (aws-sdk-lex-runtime-v2). It also adds integration tests covering the following patterns:

Non-streaming operation using recognize_text
Bidirectional streaming operation using start_conversation (TEXT mode)

A setup script at tests/setup_resources.py creates the required AWS resources (IAM role, Lex V2 bot, en_US locale with a Greeting intent and closing response).

This branch will be rebased once the release automation publishes the client.

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

arandito · 2026-04-09T16:36:18Z

...changes/next-release/aws-sdk-lex-runtime-v2-api-change-fa23e4248cb149cfacb71f203f455e83.json

@@ -0,0 +1,4 @@
+{


Do we need this changelog entry? Our release automation should handle new client setup, including initial versioning and changelog entries. We will have merge conflicts if the wording if different or we may have repeated entries because the uuid in the newly generated entry is different.

arandito · 2026-04-09T16:48:06Z

clients/aws-sdk-lex-runtime-v2/CHANGELOG.md

Same comment as before. This should be done by our release automation.

arandito · 2026-04-10T15:34:12Z

clients/aws-sdk-lex-runtime-v2/README.md

@@ -0,0 +1,10 @@
+# Code generated by smithy-python-codegen DO NOT EDIT.


Anyway we can avoid this header on the package README? This will also appear on the PyPI page for the package.

arandito · 2026-04-10T15:53:29Z

clients/aws-sdk-lex-runtime-v2/tests/setup_resources.py

+    return bot_id, bot_alias_id, locale_id
+
+
+def _wait_for_bot(lex, bot_id: str, timeout: int = 60) -> None:


We should use our waiters instead of a custom wait function. Waiters poll AWS resources until they become available so it's meant for cases like these. According to the boto3 docs, we have a bot_available waiter that waits until a bot is available after its created. We can probably do something like this:

response = lex.create_bot( botName=bot_name, roleArn=role_arn, dataPrivacy={"childDirected": False}, idleSessionTTLInSeconds=300, ) bot_id = response["botId"] print(f"Created bot: {bot_id}") lex.get_waiter("bot_available").wait( botId=bot_id, WaiterConfig=WAITER_CONFIG, )

arandito · 2026-04-10T15:56:53Z

clients/aws-sdk-lex-runtime-v2/tests/setup_resources.py

+    raise TimeoutError("Bot did not become available")
+
+
+def _wait_for_bot_locale(


Same here, we should be should be using waiters.

I see this functions handles two cases: 1) checking that the locale is created and 2) checking that it's built. These two cases should be handled by the bot_locale_created and bot_locale_built waiters.

arandito · 2026-04-10T16:25:12Z

clients/aws-sdk-lex-runtime-v2/tests/integration/__init__.py

+BOT_ALIAS_ID = "TSTALIASID"
+LOCALE_ID = "en_US"


nit: We are setting these up again instead of using the output from setup_resources.py which can introduce some drift.

arandito · 2026-04-10T16:38:29Z

clients/aws-sdk-lex-runtime-v2/pyproject.toml

+
+dependencies = [
+    "smithy_aws_core[eventstream, json]~=0.4.0",
+    "smithy_core~=0.3.0",


When I pulled down these changes, installed the client locally, and tried to run the integ tests, I got this error:

TypeError: APIOperation.__init__() got an unexpected keyword argument 'error_schemas'

This is because the error_schemas field was introduced in smithy-core 0.4.0 which was released on Tuesday. However, the codegen changes to generate these were merged as part of this commit on 3/31.

I think this client was created in between the actual release of smithy-core and the codegen merge. Let's regenerate the client using the latest release to make sure all dependencies are up-to-date for testing.

arandito · 2026-04-10T16:52:32Z

clients/aws-sdk-lex-runtime-v2/tests/integration/__init__.py

+from aws_sdk_lex_runtime_v2.client import LexRuntimeV2Client
+from aws_sdk_lex_runtime_v2.config import Config
+
+BOT_ID = os.environ["LEX_BOT_ID"]


I prefer if we retrieved the env variables in the tests themselves with error handling for cases where the user did not set up the resources.

Right now if I run these tests without setup I get:

================================== ERRORS ================================== ____ ERROR collecting tests/integration/test_bidirectional_streaming.py ____ ../../../../../.local/share/uv/python/cpython-3.12.9-macos-aarch64-none/lib/python3.12/importlib/__init__.py:90: in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <frozen importlib._bootstrap>:1387: in _gcd_import ??? <frozen importlib._bootstrap>:1360: in _find_and_load ??? <frozen importlib._bootstrap>:1310: in _find_and_load_unlocked ??? <frozen importlib._bootstrap>:488: in _call_with_frames_removed ??? <frozen importlib._bootstrap>:1387: in _gcd_import ??? <frozen importlib._bootstrap>:1360: in _find_and_load ??? <frozen importlib._bootstrap>:1331: in _find_and_load_unlocked ??? <frozen importlib._bootstrap>:935: in _load_unlocked ??? <frozen importlib._bootstrap_external>:999: in exec_module ??? <frozen importlib._bootstrap>:488: in _call_with_frames_removed ??? tests/integration/__init__.py:11: in <module> BOT_ID = os.environ["LEX_BOT_ID"] ^^^^^^^^^^^^^^^^^^^^^^^^ <frozen os>:714: in __getitem__ ??? E KeyError: 'LEX_BOT_ID' ========================= short test summary info ========================== ERROR tests/integration/test_bidirectional_streaming.py - KeyError: 'LEX_BOT_ID' !!!!!!!!!!!!!!!!!! Interrupted: 1 error during collection !!!!!!!!!!!!!!!!!! ============================= 1 error in 0.15s =============================

The error is not handled cleanly and the user has to look for where LEX_BOT_ID is set, which isn't in the test.

If I gracefully handle it in the test similar to our transcribe streaming tests:

================================= FAILURES ================================= _________________________ test_start_conversation __________________________ async def test_start_conversation() -> None: """Test bidirectional streaming StartConversation operation.""" client = create_lex_client("us-east-1") bot_id = os.environ.get("LEX_BOT_ID") if not bot_id: > pytest.fail("LEX_BOT_ID environment variable not set") E Failed: LEX_BOT_ID environment variable not set tests/integration/test_bidirectional_streaming.py:98: Failed ========================= short test summary info ========================== FAILED tests/integration/test_bidirectional_streaming.py::test_start_conversation - Failed: LEX_BOT_ID environment variable not set ============================ 1 failed in 0.13s =============================

The failure point is clear and easier to debug.

arandito · 2026-04-10T17:07:38Z

clients/aws-sdk-lex-runtime-v2/tests/integration/test_non_streaming.py

+
+    intent_names = [i.intent.name for i in response.interpretations if i.intent]
+    assert "Greeting" in intent_names
+    assert "FallbackIntent" in intent_names


Is this fallback intent always returned?

arandito · 2026-04-10T17:13:20Z

clients/aws-sdk-lex-runtime-v2/tests/integration/test_bidirectional_streaming.py

+        return got_text_response, messages
+
+    async for event in output_stream:
+        if isinstance(event, StartConversationResponseEventStreamTextResponseEvent):


Why do we not raise a runtime error when there is an unexpected event similar to current bidi integ tests: https://github.com/awslabs/aws-sdk-python/blob/develop/clients/aws-sdk-bedrock-runtime/tests/integration/test_bidirectional_streaming.py#L221-L223

Your are right to point this out. And I'll add checks for other possible events as well.

Add generated Lex Runtime V2 client with integration tests

fe49e0c

Alan4506 requested a review from a team as a code owner April 3, 2026 19:31

Add change entry for the new lex package

ab0e01b

arandito reviewed Apr 10, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add generated Lex Runtime V2 client with integration tests#51

Add generated Lex Runtime V2 client with integration tests#51
Alan4506 wants to merge 2 commits intoawslabs:developfrom
Alan4506:feat/lex-runtime-v2-client

Alan4506 commented Apr 3, 2026 •

edited

Loading

Uh oh!

arandito Apr 9, 2026

Uh oh!

arandito Apr 9, 2026

Uh oh!

arandito Apr 10, 2026

Uh oh!

arandito Apr 10, 2026

Uh oh!

arandito Apr 10, 2026

Uh oh!

arandito Apr 10, 2026 •

edited

Loading

Uh oh!

arandito Apr 10, 2026

Uh oh!

arandito Apr 10, 2026

Uh oh!

arandito Apr 10, 2026

Uh oh!

arandito Apr 10, 2026

Uh oh!

Alan4506 Apr 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		@@ -0,0 +1,10 @@
		# Code generated by smithy-python-codegen DO NOT EDIT.

		return bot_id, bot_alias_id, locale_id


		def _wait_for_bot(lex, bot_id: str, timeout: int = 60) -> None:

		raise TimeoutError("Bot did not become available")


		def _wait_for_bot_locale(

		BOT_ALIAS_ID = "TSTALIASID"
		LOCALE_ID = "en_US"

Conversation

Alan4506 commented Apr 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

arandito Apr 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Alan4506 commented Apr 3, 2026 •

edited

Loading

arandito Apr 10, 2026 •

edited

Loading