The documentation you are viewing is for Dapr v1.4 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Dapr integrates with external resources to allow apps to both be triggered by external events and interact with the resources. Each binding component has a name and this name is used when interacting with the resource.
As with other building block components, binding components are extensible and can be found in the components-contrib repo.
A binding in Dapr is described using a
Component file with the following fields:
apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: <NAME> namespace: <NAMESPACE> spec: type: bindings.<NAME> version: v1 metadata: - name: <KEY> value: <VALUE> - name: <KEY> value: <VALUE> ...
The type of binding is determined by the
type field, and things like connection strings and other metadata are put in the
apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: <NAME> namespace: <NAMESPACE> spec: type: bindings.azure.blobstorage version: v1 metadata: - name: storageAccount value: myStorageAccountName - name: storageAccessKey value: *********** - name: container value: container1 - name: decodeBase64 value: <bool> - name: getBlobRetryCount value: <integer>
Apply the configuration
Once you have created the component’s YAML file, follow these instructions to apply it based on your hosting environment:
To run locally, create a
components dir containing the YAML file and provide the path to the
dapr run command with the flag
To deploy in Kubernetes, assuming your component file is named
kubectl apply -f mybinding.yaml
Visit the bindings reference for a full list of supported resources.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.