-
Notifications
You must be signed in to change notification settings - Fork 165
Documentation: Unclear how to use events signature-type and test pubsub #37
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
Comments
Hey @comolongo, Looks like it uses the HTTP signature, but it could be useful for a local dev workflow. |
hi, |
@Sabyasachi2k Does this guide help? We're working on an event guide. I agree it would be useful. |
@grant Thank you for the link.
Maybe a little background of what I am trying to do Expecting that every time a particular image is pushed to the repo, this function would be called and the data element would be as per the link above. Am I totally off? |
I don't know at the moment. Node functions for Pub/Sub triggers should look like this: If we think there is a bug with following that code, we should file a bug with expected/actual behavior that might be in this framework or elsewhere. |
Thanks a lot @grant |
There's a feedback button on the page for creating the bug report. |
* Added new section in README.md to clarify how to do local testing of event functions * Line regarding #37 removed
Hi,
I was able to setup and do local testing using http signature. However my goal is to do local development on a cloud function that consumes PubSub. What is the best development workflow for this?
I was thinking I may need to set signature-type to event, and somehow pass in a mock pubsub event object, how the current documentation doesn't give me many clues. Could someone point me the way?
Thanks!
The text was updated successfully, but these errors were encountered: