Skip to content
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

fix: Improved AWS Lambda event detection #2496

Closed
wants to merge 1 commit into from

Conversation

jsumners-nr
Copy link
Contributor

@jsumners-nr jsumners-nr commented Aug 20, 2024

This PR resolves #2489.

) {
result = true
}
const v1Keys = [
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't find any information on what AWS does when some field from this list is not included in the payload. Does it send with field: null? Or does it completely omit the field. We are assuming that it sends field: null with this implementation, because the v1 example shows some such fields.


// Event used when one Lambda directly invokes another Lambda.
// https://docs.aws.amazon.com/lambda/latest/dg/invocation-async-retain-records.html#invocation-async-destinations
const lambaV1InvocationEvent = {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not completely convinced this is the only payload shape that Lambda sends with direct invocations. But I can't find any other documentation to prove that.

@jsumners-nr jsumners-nr deleted the issue-2291 branch August 20, 2024 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Error when using lambda destination: Cannot read properties of undefined (reading 'pathname')
1 participant