-
Notifications
You must be signed in to change notification settings - Fork 97
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
Docker image out of date? #439
Comments
Hey @kenfdev, glad you like the Event Gateway! Thanks for filing this ticket with detailed repro steps. We're currently doing some minor re-working of the internals of the Event Gateway, including the subscription model. Some of this work is finished, and some is in-progress. As you've noted, the README includes instructions for the new subscription model but the latest published Docker image does not have these updates. If you're using the {
"event": "http",
"functionId": "echo",
"path": "/echo",
"method": "POST"
} We're looking to finish up the subscription model changes and release a 0.8 version within the next 1-2 weeks. |
@alexdebrie Thanks for the fast response! Glad to know and confirm what is happening. |
@kenfdev You're welcome! I'll go ahead and close it. We'll try to do a better job keeping docs in line with the latest release going forward. Feel free to hit us up with any other questions! |
First of all, thanks for all the hard work and the awesome project.
This is a (kind of) Bug Report
For bug reports, please answer following questions:
As explained here, I tried to create a sync subscription via HTTP event but failed.
The request payload is like the following:
I've changed the
eventType
key toevent
and the request succeeded.The next issue is that even though I invoke the function, I only receive a
202 Accepted
. I expected to see a 200 with a response. It seemed like it wasn't registered as ansync
function. At the end, I changedhttp.request
tohttp
. So my final request is as follows:What did you expect should have happened?
Expected everything to work without the workarounds.
What was the version you used?
The container image is
As explained above:
For feature proposals, please answer the following question:
Similar or dependent issues:
latest
image.The text was updated successfully, but these errors were encountered: