mirror of
https://github.com/serverless/serverless.git
synced 2025-12-08 19:46:03 +00:00
- removed erroneous statement about "context and event properties" in mock event data files - added example data.json @TODO: the `invoke` docs should be the main source of truth here, the `invoke local` docs should describe *only what's different from invoke* and defer to `invoke` for the rest. Duplicating across the two files is not ideal.
3.4 KiB
3.4 KiB
Read this on the main serverless docs site
AWS - Invoke
Invokes deployed function. It allows to send event data to the function, read logs and display other important information of the function invocation.
serverless invoke [local] --function functionName
Options
--functionor-fThe name of the function in your service that you want to invoke. Required.--stageor-sThe stage in your service you want to invoke your function in.--regionor-rThe region in your stage that you want to invoke your function in.--dataor-dString data to be passed as an event to your function. By default data is read from standard input.--pathor-pThe path to a json file with input data to be passed to the invoked function. This path is relative to the root directory of the service.--typeor-tThe type of invocation. EitherRequestResponse,EventorDryRun. Default isRequestResponse.--logor-lIf set totrueand invocation type isRequestResponse, it will output logging data of the invocation. Default isfalse.
Provided lifecycle events
invoke:invoke
Invoke Local
Invokes a function locally for testing and logs the output. You can only invoke Node.js runtime locally at the moment. Keep in mind that we mock the context with simple mock data.
serverless invoke local --function functionName
Options
--functionor-fThe name of the function in your service that you want to invoke locally. Required.--pathor-pThe path to a json file holding input data to be passed to the invoked function as theevent. This path is relative to the root directory of the service.--dataor-dString data to be passed as an event to your function. Keep in mind that if you pass both--pathand--data, the data included in the--pathfile will overwrite the data you passed with the--dataflag.
Examples
AWS
serverless invoke --function functionName --stage dev --region us-east-1
This example will invoke your deployed function named functionName in region us-east-1 in stage dev. This will
output the result of the invocation in your terminal.
Function invocation with data
serverless invoke --function functionName --stage dev --region us-east-1 --data "hello world"
Function invocation with data from standard input
node dataGenerator.js | serverless invoke --function functionName --stage dev --region us-east-1
Function invocation with logging
serverless invoke --function functionName --stage dev --region us-east-1 --log
Just like the first example, but will also outputs logging information about your invocation.
Function invocation with data passing
serverless invoke --function functionName --stage dev --region us-east-1 --path lib/data.json
This example will pass the json data in the lib/data.json file (relative to the root of the service) while invoking
the specified/deployed function.
Example data.json
{
"resource": "/",
"path": "/",
"httpMethod": "GET",
// etc. //
}