Skip to content

Latest commit

 

History

History
39 lines (33 loc) · 1.98 KB

eventhubs.md

File metadata and controls

39 lines (33 loc) · 1.98 KB
Raw

Azure Event Hubs Binding Spec

See this for instructions on how to set up an Event Hub.

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: <NAME>
  namespace: <NAMESPACE>
spec:
  type: bindings.azure.eventhubs
  metadata:
  - name: connectionString      # Azure EventHubs connection string
    value: "Endpoint=sb://****"
  - name: consumerGroup         # EventHubs consumer group
    value: "group1"
  - name: storageAccountName    # Azure Storage Account Name
    value: "accountName"   
  - name: storageAccountKey     # Azure Storage Account Key
    value: "accountKey"                
  - name: storageContainerName  # Azure Storage Container Name
    value: "containerName"    
  - name: partitionID           # (Optional) PartitionID to send and receive events
    value: 0
  • connectionString is the EventHubs connection string. Note that this is the EventHub itself and not the EventHubs namespace. Make sure to use the child EventHub shared access policy connection string.
  • consumerGroup is the name of an EventHubs Consumer Group to listen on.
  • storageAccountName Is the name of the account of the Azure Storage account to persist checkpoints data on.
  • storageAccountKey Is the account key for the Azure Storage account to persist checkpoints data on.
  • storageContainerName Is the name of the container in the Azure Storage account to persist checkpoints data on.
  • partitionID (Optional) ID of the partition to send and receive events.

Note: In production never place passwords or secrets within Dapr components. For information on securely storing and retrieving secrets refer to Setup Secret Store

Output Binding Supported Operations

  • create