You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with a Dapr application, and I'm having trouble with my topic subscription setup in the following code:
builder.MapControllerRoute("ReceiveFeedEvent", "/ReceiveFeedEvent").WithTopic(new TopicOptions { PubsubName = Config.DaprAlertFeedConsumerName, Name = configuration[Config.AlertFeedTopicNameKey], Metadata = new Dictionary<string, string>() { { "consumerID","feed"} } });
I'm using this configuration to set up a route that receives events from a specified topic. However, it seems that the consumerID I specified in the metadata does not work as expected.
Kindly help if there is a specific format or requirement for the consumerID in Dapr subscriptions?
I am trying to subscribe multiple subscription under one topic using Dapr.
The text was updated successfully, but these errors were encountered:
@mshashi0306
I believe the consumer ID should be populated in the YAML component's metadata field as indicated in the Azure Service Bus Topic component spec, not in the topic options in the C# project.
Yes @WhitWaldo , I have tried adding the consumerId to the YAML file, but it requires creating multiple service bus component files for each subscription.
I’m looking to have a single YAML file without the consumerId, as I have multiple subscriptions under one topic.
I've raised your question on Discord in hopes someone there knows as I'm afraid I don't immediately see how you'd pass the consumer ID in any but a declarative instance.
I'm working with a Dapr application, and I'm having trouble with my topic subscription setup in the following code:
builder.MapControllerRoute("ReceiveFeedEvent", "/ReceiveFeedEvent").WithTopic(new TopicOptions { PubsubName = Config.DaprAlertFeedConsumerName, Name = configuration[Config.AlertFeedTopicNameKey], Metadata = new Dictionary<string, string>() { { "consumerID","feed"} } });
I'm using this configuration to set up a route that receives events from a specified topic. However, it seems that the consumerID I specified in the metadata does not work as expected.
Kindly help if there is a specific format or requirement for the consumerID in Dapr subscriptions?
I am trying to subscribe multiple subscription under one topic using Dapr.
The text was updated successfully, but these errors were encountered: