CodeGenieApp / CodeGenieApp/serverless-express

'Unable to determine event source based on event.' Lambda to Lambda Invoke

未关闭
#548 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
JavaScript
星标
5.3k
派生
676
PR 合并指标
30 天内没有已合并 PR

描述

Hello,
I am trying to catch event parameters from Lambda A which invokes Lambda B with event parameter.

I was trying to use getCurrentInvoke() at the global level to catch it, but unfortunately it was futile.

How can I catch event parameter passed when invoked by another Lambda?

The Lambda b is for my slack app that I deployed onto Lambda.

at the end of the file it has this exports.handler

```javascript
module.exports.handler = serverlessExpress({
app: receiver.app,
});
```

I believe this is the place where I need to grab the event parameter. So far, what I've done is this :
```javascript
exports.handler = async (event, context) => {
console.log(event, context);
return serverlessExpress({
app: receiver.app,
});
};

-----------

module.exports.handler = async (event, context) => {
console.log(event, context);
return serverlessExpress({
app: receiver.app,
});
};
```
none worked out for me :(
I am very new to this serverless and backend logic stuff so please shed some knowledge! I greatly appreaciate!

贡献指南

打开贡献指南

调研方向

The relevant entry point is the exported handler using serverlessExpress({ app: receiver.app }); start by tracing the Lambda-to-Lambda invocation and the handler signature shown in the issue. Done means identifying where the invoked event is available and documenting or reproducing the expected behavior, but no target code change is specified.

由索引模型根据 Issue 内容生成。

评估

技术栈
aws, express, javascript, node.js
领域
backend, cloud
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。