dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update EventHub single partition id spec (#449) 

Updated EventHub binding spec to include the information on sending the event to a single partition.
This commit is contained in:
Sivamuthu Kumar 2020-03-20 18:45:24 -04:00 committed by GitHub
parent f0a78133b9
commit eaed191713
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
reference/specs/bindings/eventhubs.md
View File

@ -1,6 +1,6 @@
# Azure Event Hubs Binding Spec
See (this)[https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-dotnet-framework-getstarted-send] for instructions on how to set up an Event Hub.
See [this](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-dotnet-framework-getstarted-send) for instructions on how to set up an Event Hub.
```yml
apiVersion: dapr.io/v1alpha1
@ -19,7 +19,9 @@ spec:
- name: storageAccountKey # Azure Storage Account Key
value: "accountKey"
- name: storageContainerName # Azure Storage Container Name
value: "containerName"
value: "containerName"
- name: partitionID # (Optional) PartitionID to send and receive events
value: 0
```
- `connectionString` is the [EventHubs connection string](https://docs.microsoft.com/en-us/azure/event-hubs/authorize-access-shared-access-signature). Note that this is the EventHub itself and not the EventHubs namespace. Make sure to use the child EventHub shared access policy connection string.
@ -27,5 +29,6 @@ spec:
- `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 securly storing and retrieving secrets refer to [Setup Secret Store](../../../howto/setup-secret-store)