gdibben 6b84ae69a0 Prevent --json from prompting interactively on a 403 ...

Per review: --json still went through _create_host_backend_client
and _call_host_backend_with_optional_tenant, both of which prompt
interactively (writing to stdout, reading stdin) when the module-
level _no_input flag is left at its default False. deploy_listeners_
list never set it, unlike the main deploy command, so a missing API
key or an org-scoped key without LANGSMITH_TENANT_ID would corrupt
the JSON output with warning text and could hang waiting for input
that a scripted invocation never provides.

Sets _no_input = json_output at the top of the command, same pattern
_deploy_cmd already uses, so both paths raise a ClickException to
stderr instead. Added a regression test that fails without the fix
(click.prompt is genuinely invoked) and passes with it.

2026-10-08 08:26:40 +01:00

..

integration_tests

cli[minor]: Add langgraph new command (#2369)

2024-11-12 14:30:51 -05:00

unit_tests

Prevent --json from prompting interactively on a 403

2026-10-08 08:26:40 +01:00

__init__.py

libs: add cli, sdk-py, sdk-js and move core langgraph

2024-06-17 20:37:25 -04:00