Dapr extension pub/sub error: no pubsub is configured

When running Type with the Dapr extension using pub/sub, I got an exception with daprClient.PublishEventAsync("pubsub", "weather", weather):

Message=Publish operation failed: the Dapr endpoint indicated a failure.
Source=Dapr.Client
Inner Exception: RpcException: Status(StatusCode="FailedPrecondition", Detail="no pubsub is configured")

I do not get the exception when running dapr directly: dapr run --app-id publisher -- dotnet run

I can verify in the Components tab of the Dapr Dashboard that pubsub is configured properly.

_Originally posted by @tonysneed in https://github.com/dotnet/tye/issues/984#issuecomment-800631405_

[tonysneed]

@jkotalik Are you able to reproduce the error using the steps I provided? This is preventing me from using Tye to debug Dapr pub/sub using Visual Studio. Thanks.

[philliphoff]

@tonysneed I believe this is/was expected behavior. At the time this issue was filed, Tye invoked the sidecar (daprd) directly. daprd would not load any components if no --components-path was specified (which is the case if no components-path exists in the tye.yaml). However, dapr run invokes the sidecar and passes a default --components-path argument (~/.dapr/components) if not given a specific value. Since Dapr initialization typically scaffolds a default pubsub component, your application likely worked, despite actually using a different component configuration than expected (the one in your repo). By adding the components-path to tye.yaml, daprd ends up with a specific --components-path.

In any case, Tye now uses dapr run rather than daprd directly, so applications will use the default Dapr components (just like they would on the command line) unless redirected by a components-path property set in tye.yaml. In other words, if you have specific Dapr component configuration in your repo, you should set components-path in tye.yaml.

Let me know if that makes sense; if so, I’ll close this issue.