Read this on the main serverless docs site¶
OpenWhisk - Invoke¶
Invokes a deployed function. You can send event data, read logs and display other important information of the function invocation.
Options¶
--functionor-fThe name of the function in your service that you want to invoke. Required.--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.
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. This path is relative to the root directory of the service. The json file should have event and context properties to hold your mocked event and context data.--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¶
Apache OpenWhisk¶
This example will invoke your deployed function on the configured platform endpoint. This will output the result of the invocation in your terminal.
Function invocation with data¶
Function invocation with data from standard input¶
Function invocation with logging¶
Just like the first example, but will also outputs logging information about your invocation.
Function invocation with data passing¶
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.