oura 2.2.0

The tail of Cardano
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

---
title: Google Cloud Functions
sidebar:
  label: Gcp Functions
---

A sink that sends each event to a cloud function. Each event is json-encoded and sent as a POST request.

## Configuration

```toml
[sink]
type = "GcpCloudFunction"
url = "https://REGION-PROJECT_ID.cloudfunctions.net/FUNCTION_NAME"
timeout = 30000
authentication = true

[sink.headers]
extra_header_1 = "abc"
extra_header_2 = "123"
```

### Section: `sink`

- `type`: the literal value `GcpCloudFunction`
- `url`: Your function url
- `timeout` (optional): the timeout value for the HTTP response in milliseconds. Default value is `30000`.
- `authentication` (optional): a flag that, when set to `true`, attaches a GCP identity token as the 'Authorization' HTTP header (see _GCP Authentication_ below). Default value is `false`.
- `headers` (optional): key-value map of extra headers to pass in each HTTP call

### GCP Authentication

The GCP authentication process relies on the following conventions:

- If the `GOOGLE_APPLICATION_CREDENTIALS` environmental variable is specified, the value will be used as the file path to retrieve the JSON file with the credentials.