InfluxDB binding spec
Detailed documentation on the InfluxDB binding component
Component format
To setup InfluxDB binding create a component of type bindings.influx
. See this guide on how to create and apply a binding configuration.
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
namespace: <NAMESPACE>
spec:
type: bindings.influx
version: v1
metadata:
- name: url # Required
value: <INFLUX-DB-URL>
- name: token # Required
value: <TOKEN>
- name: org # Required
value: <ORG>
- name: bucket # Required
value: <BUCKET>
Warning
The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.
Spec metadata fields
Field | Required | Binding support | Details | Example |
---|---|---|---|---|
url | Y | Output | The URL for the InfluxDB instance | “http://localhost:8086“ |
token | Y | Output | The authorization token for InfluxDB | “mytoken” |
org | Y | Output | The InfluxDB organization | “myorg” |
bucket | Y | Output | Bucket name to write to | “mybucket” |
Binding support
This component supports output binding with the following operations:
create
query
Query
In order to query InfluxDB, use a query
operation along with a raw
key in the call’s metadata, with the query as the value:
curl -X POST http://localhost:3500/v1.0/bindings/myInfluxBinding \
-H "Content-Type: application/json" \
-d "{
\"metadata\": {
\"raw\": "SELECT * FROM 'sith_lords'"
},
\"operation\": \"query\"
}"
Related links
- Basic schema for a Dapr component
- Bindings building block
- How-To: Trigger application with input binding
- How-To: Use bindings to interface with external resources
- Bindings API reference
Last modified June 23, 2022: Merge pull request #2550 from ItalyPaleAle/cosmosdb-harcoded-dapr-version (cf03237)