Lambda functions in the AWS documentation and examples have a signature (event, context) => result. The content of the event argument seems to depend on how the function is invoked, e.g. invocations from the AWS command line interface put just the payload in event, whereas if the function is invoked via a Lambda function URL, the event argument contains full information about the HTTP request. (All this subject to disclaimers of "based on what I'm seeing today but I am not an expert" :) )
So, say I use Jot to wrap up a Julia function fun--whether defined in a package or a script or anything else--which takes a single argument of type InputType.
When the resulting Lambda function is invoked, how is the Julia call fun(arg::InputType) constructed? Does this depend on how the function is invoked?
Correspondingly, if one wants to invoke the resulting Lambda, how does the payload need to be structured? Does this depend on whether the invocation is by AWS triggered event (e.g. API gateway), direct function URL, AWS CLI, ... ?
Lambda functions in the AWS documentation and examples have a signature
(event, context) => result. The content of theeventargument seems to depend on how the function is invoked, e.g. invocations from the AWS command line interface put just the payload inevent, whereas if the function is invoked via a Lambda function URL, theeventargument contains full information about the HTTP request. (All this subject to disclaimers of "based on what I'm seeing today but I am not an expert" :) )So, say I use Jot to wrap up a Julia function
fun--whether defined in a package or a script or anything else--which takes a single argument of typeInputType.fun(arg::InputType)constructed? Does this depend on how the function is invoked?Thanks!