# Functions

Kubemq gcp Cloud Functions target connector allows services using kubemq server to access call a function target on gcp Cloud Function. The connector synchronously invokes a deployed Cloud Function, very limited traffic is allowed 16 per 100 seconds.

## Prerequisites

The following are required to run the redis target connector:

* kubemq cluster
* Gcp Cloud function targe.
* kubemq-targets deployment

## Configuration

Kafka source connector configuration properties:

| Properties Key  | Required | Description                                    | Example       |
| --------------- | -------- | ---------------------------------------------- | ------------- |
| project         | yes      | gcp project name                               | "testproject" |
| credentials     | yes      | gcp service account key location (json)        | "TestTopic"   |
| location\_match | no       | match missing function location (default true) | "true"        |

Example:

```yaml
bindings:
  - name: kubemq-query
    source:
      kind: kubemq.kubemq.query
      name: kubemq-query
      properties:
        address: "kubemq-cluster:50000"
        client_id: "kubemq-query-gcpfucntions-connector"
        auth_token: ""
        channel: "query.gcp.functions"
        group:   ""
        auto_reconnect: "true"
        reconnect_interval_seconds: "1"
        max_reconnects: "0"
    target:
      kind: gcp.cloudfunctions
      name: target-gcp-couldfunctions
      properties:
        project: "testproject"
        credentials: "myKey"
        location_match: "true"
```

## Usage

### Get Request

Get request metadata setting:

| Metadata Key | Required | Description                                          | Possible values  |
| ------------ | -------- | ---------------------------------------------------- | ---------------- |
| name         | yes      | name of the gcp function                             | "test\_function" |
| project      | no       | gcp project name (override parent value)             | "testproject1"   |
| location     | no       | gcp project location (missing value will be matched) | "us-central1"    |

Example:

```javascript
{
  "metadata": {
    "name": "test_function",
    "location": "us-central1"    
  },
  "data": "eyJtZXNzYWdlIjoidGVzdCJ9"
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kubemq.io/configuration/connectors/kubemq-targets/gcp/cloudfunctions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.