Consider setting DAPR_HTTP_PORT and DAPR_GRPC_PORT in DaprDistributedApplicationLifecycleHook #4077
Labels
area-app-model
Issues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication
area-dapr
Currently, when adding a Dapr sidecar, the DAPR_HTTP_ENDPOINT and DAPR_GRPC_ENDPOINT environment variables are set:
aspire/src/Aspire.Hosting.Dapr/DaprDistributedApplicationLifecycleHook.cs
Lines 148 to 152 in 31ce95b
Some apps may instead rely on DAPR_HTTP_PORT and/or DAPR_GRPC_PORT and will therefore fail.
See also:
https://github.com/dapr/dotnet-sdk/blob/ba1341510bfc81f0e1ba4687539ec49aa90abc4e/src/Shared/DaprDefaults.cs#L63-L76
The text was updated successfully, but these errors were encountered: