[Content]: GCP Cloud Functions doc doesn't explain request format

[borenstein]

What article on segment.com/docs is affected?

https://segment.com/docs/connections/destinations/catalog/google-cloud-function/

What part(s) of the article would you like to see updated?

When writing a GCP cloud function to handle inbound Segment data, I need to know what the body of the request is going to look like so that I can write handlers for it. Without that, I have to find out by trial and error, creating an event that just dumps everything to the console. That's very silly!

Additional information

No response

[markzegarelli]

Hi @borenstein, thanks for submitting this issue.

Requests to destinations vary widely, depending on the way the Source is configured, and the type of event that is sent.

I think your best bet here will be to use a combination of the Source Debugger, and Destination Event Tester as explained in Testing Connections. The Source Debugger, in particular, shows the raw content of the event data received by Segment, which is then sent on to the destination.

I will add this detail to the doc, for future reference.

[borenstein]

Great. Yes, clarifying that the request body will be identical to what you see in the source debugger (if that is true, which it seems to be), would have saved me a couple hours today.

…

On Thu, Sep 30, 2021, 12:53 PM markzegarelli ***@***.***> wrote: Hi @borenstein <https://github.com/borenstein>, thanks for submitting this issue. Requests to destinations vary widely, depending on the way the Source is configured, and the type of event that is sent. I think your best bet here will be to use a combination of the Source Debugger, and Destination Event Tester as explained in Testing Connections <https://segment.com/docs/connections/test-connections/>. The Source Debugger, in particular, shows the raw content of the event data received by Segment, which is then sent on to the destination. I will add this detail to the doc, for future reference. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1929 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABB6BH5CFZC6KE2I5YPCT3TUESIXZANCNFSM5FCN3AWA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[markzegarelli]

Thanks for confirming, and apologies for the lack of clarity.

We will add this detail to the doc.