Skip to content

Add proxy support and tests for Lambda service#128

Open
whummer wants to merge 1 commit intomainfrom
add-lambda-proxy-tests
Open

Add proxy support and tests for Lambda service#128
whummer wants to merge 1 commit intomainfrom
add-lambda-proxy-tests

Conversation

@whummer
Copy link
Member

@whummer whummer commented Feb 7, 2026

Add Lambda resource matching in the proxy handler (FunctionName/ARN-based) and comprehensive integration tests covering basic proxying, read-only mode, and resource name pattern matching.

Add Lambda resource matching in the proxy handler (FunctionName/ARN-based)
and comprehensive integration tests covering basic proxying, read-only mode,
and resource name pattern matching.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@whummer whummer force-pushed the add-lambda-proxy-tests branch from 1204f7b to 976911c Compare February 8, 2026 13:11
@whummer whummer marked this pull request as ready for review February 27, 2026 12:23
"PartiQLSelect",
}:
return True
if context.service.service_name == "lambda" and operation_name in {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not quite sure if we should consider the invoking of lambdas as a "read" operation.
Running a lambda can have many side-effects. I wouldn't expect the lambda to be called when I use read-only mode. Especially in the era of AI-agents, this can be very problematic for a user that may have thought that they give read-only access to the proxy.
Could we introduce some other mode specifically for cases like this? (like execute or invoke?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants