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

Support for function invocations not made via API Gateway #12

Closed
dominique-pfister opened this issue Apr 30, 2021 · 0 comments · Fixed by #15
Closed

Support for function invocations not made via API Gateway #12

dominique-pfister opened this issue Apr 30, 2021 · 0 comments · Fixed by #15
Assignees
Labels
question Further information is requested

Comments

@dominique-pfister
Copy link
Contributor

dominique-pfister commented Apr 30, 2021

When I try invoking my hedy deployed function in the AWS console, I get a TypeError indicating that some information is missing to build the context passed to the universal main, e.g. the event.requestContext:

const request = new Request(`https://${event.requestContext.domainName}${event.rawPath}${event.rawQueryString ? '?' : ''}${event.rawQueryString}`, {

I understand that it is not possible to create a resolver without a requestContext, but in order to easily build an AWS trigger for a function that does not require the resolver, it would be ideal if the missing information is not provided, and using a resolver would fail in that particular situation.

On the other hand, I can also try to create an AWS trigger and feed the expected JSON into the event payload.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant