admin管理员组

文章数量:1123140

So I've created a resource pubsub.yaml which references a Service Bus Connection String. It works fine on my local machine using .NET Aspire, however when I use the az up (Container Apps) it fails. In the Aspire Dashboard I can see the daprstore is running but the service itself is stuck on a pending state. In Container Apps I can also see that the Dapr Components is set to redis instead of Service Bus. Any idea what's going wrong?

I tried the following code below:

var pubSub = builder.AddDaprPubSub("pubsub");

var apiService = builder.AddProject<Projects.SomeService>("someservice")
    .WithDaprSidecar()
    .WithReference(pubSub);

builder.Build().Run();

Service Bus YAML:

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: pubsub
spec:
  type: pubsub.azure.servicebus
  version: v1
  metadata:
  - name: connectionString
    value: "Endpoint=someEndPoint"
  - name: topic
    value: "someTopic"
  - name: subscriptionName
    value: "someSubscriptionName"

本文标签： azureWhy is Dapr PubSub set to redis instead of Service Bus in ContainerApps (NET Aspire)Stack Overflow

版权声明：本文标题：azure - Why is Dapr PubSub set to redis instead of Service Bus in ContainerApps (.NET Aspire) - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1736552531a1944531.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。