Skip to content

Commit 12d75cc

Browse files
author
markzegarelli
authored
Merge pull request #1949 from segmentio/1929_add-testing-detail
Fixes 1929
2 parents b76c021 + 90a21b0 commit 12d75cc

File tree

1 file changed

+12
-11
lines changed
  • src/connections/destinations/catalog/google-cloud-function

1 file changed

+12
-11
lines changed

src/connections/destinations/catalog/google-cloud-function/index.md

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -21,17 +21,18 @@ Before you can process events from Segment, you must provide a Google Cloud Func
2121

2222
1. Go to https://cloud.google.com/functions.
2323
2. Click **VIEW CONSOLE**.
24-
![](images/gcloud1.png)
25-
2624
3. Select a project.
2725
4. Click **CREATE FUNCTION**.
28-
![](images/gcloud2.png)
2926
5. Enter a name for your function, and choose how much memory the function can use.
30-
7. In the **Trigger** field, select `HTTP`. Save the `URL` GCP gives you. You'll use this to configure the Segment destination later.
31-
8. Choose how you'll provide the function's code (in the **Source code** field) and what language the code is written in (in the **Runtime** field).
32-
9. Enter the name of the function as you defined it in your code, in the **Function to execute** field.
33-
10. Click **Create** to save your settings and create the Google Cloud Function.
34-
![](images/gcloud3.png)
27+
6. In the **Trigger** field, select `HTTP`. Save the `URL` GCP gives you. You'll use this to configure the Segment destination later.
28+
7. Choose how you'll provide the function's code (in the **Source code** field) and what language the code is written in (in the **Runtime** field).
29+
8. Enter the name of the function as you defined it in your code, in the **Function to execute** field.
30+
9. Click **Create** to save your settings and create the Google Cloud Function.
31+
32+
33+
### Test the function
34+
35+
Segment recommends that you use the Debugger of the source you intend to connect to the Google Cloud Function destination to inspect the request body of the incoming event. This allows you to build handlers in your function based on accurate incoming data. For more information, see [Testing Connections](/docs/connections/test-connections/).
3536

3637
## Configure the Google Cloud Function Destination
3738

@@ -44,7 +45,7 @@ Once you create the Google Cloud Function, you can set up a Segment destination
4445
3. Click **Configure Google Cloud Function**.
4546
4. Enter the destination settings for this GCF destination.
4647

47-
| Setting | Description |
48-
| -------- | ------------------- |
49-
| **HTTP Trigger** | The URL given under the `Trigger` section when you created the Google Cloud Function. |
48+
| Setting | Description |
49+
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
50+
| **HTTP Trigger** | The URL given under the `Trigger` section when you created the Google Cloud Function. |
5051
| **API Key** (optional) | A string to identify that a request is coming from Segment, if required by the function. <br><br>The API key is injected in the `Authorization` header as a [basic authorization header](https://en.wikipedia.org/wiki/Basic_access_authentication) without password. |

0 commit comments

Comments
 (0)