-
Notifications
You must be signed in to change notification settings - Fork 106
How to invoke a function with custom client context? #74
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
Comments
I asked AWS Support and received an answer which says there is no ways to pass client context to my function, for now. Alternatively, as a workaround, if it's possible to change function code, we can set client context in the code if no client context is given. |
Still pending actual release with this feature. I'll keep it open until next release. |
@valerena when can we expect v1.19 to be available in |
I reached out to the team in charge of maintaining those images. We'll see what they say |
The images with the new version of RIE were released and are available (https://gallery.ecr.aws/lambda/provided and also in other runtimes). |
On AWS, I'm using Lambda function which receives event data and custom client context. For local testing, I want to run
curl
and invoke function with custom client context, defined as:aws-lambda-runtime-interface-emulator/lambda/core/directinvoke/customerheaders.go
Line 15 in 5a79e1e
I dug into codes, and found aws-lambda-rie seems not to add client context to a invoke payload:
aws-lambda-runtime-interface-emulator/cmd/aws-lambda-rie/handlers.go
Lines 96 to 103 in 5a79e1e
So, is there any ways to use custom client context with aws-lambda-rie? Should I send a pull request for this? It seems that
Lambda-Runtime-Client-Context
header is related to this, but I cannot find a way to use it properly.Environment: I'm using
aws-lambda-rie
command inpublic.ecr.aws/lambda/nodejs:18.2022.12.02.19
image (https://gallery.ecr.aws/lambda/nodejs). Locally, I confirmed my function implementation can receive event data by runningcurl -XPOST "http://localhost:9000/2015-03-31/functions/function/invocations" -d '{"payload":"hello world!"}'
, but cannot receive client context by addingLambda-Runtime-Client-Context
header like-H 'Lambda-Runtime-Client-Context: { "foo":"bar" }'
. On AWS, my function can receive custom client context.The text was updated successfully, but these errors were encountered: