Closed tpankake-insight closed 3 months ago
@tpankake-insight Per the spec, the Dapr run file uses the somewhat more unwieldy daprGRPCPort
and daprHTTPPort
properties to indicate the gRPC and HTTP ports used by the Dapr sidecar.
(Closing as verified that VS was abiding by the Dapr run file spec.)
I have tried adding
grpcPort:
andhttpPort:
to the dapr.yaml file for each of my projects with a specific port number. However, when I start my services through VS, I see thedapr run
command does not include--http-port
or--grpc-port
arguments and the ports are randomly assigned and change each time I restart debugging. I need to be able to predict my http and grpc dapr ports. Is there a yaml syntax that I'm not seeing? Or is this a known issue?