dapr / dapr/dotnet-sdk

Mark WaitForSidecar check as obsolete in Dapr .NET SDKs

Open
#1,403 26 comments 0 reactions 1 assignee Claimed by @WhitWaldo View on GitHub
area/actor/client kind/enhancement
Dominant language
C#
Stars
1.2k
Forks
378
Avg merge
2d 1h
Merged PRs (30d)
6

Description

## Describe the feature
The DaprClient offers a method that enables the developer to wait for the sidecar to be ready before starting any operations, but Dapr.Workflow doesn't have any such method.

~~Perhaps it's worth looking at adding it during startup both as a method exposed to developers, but also which happens internally so that any attempt to do an actor operation is preempted until the app channel is live and then allowed to proceed.~~

After discussing this with the core team, we'll be marking `WaitForSidecar` as obsolete on the `Dapr.Client` SDK as it's not a method that developers should be using in their own applications as that's not its purpose. Rather, developers should call the SDK methods as they want and the runtime will queue and block them until it's ready to process each one - no waiting/readiness check necessary.

## Release Note
RELEASE NOTE: **UPDATE** Developers should not use `WaitForSidecar` in their applications to wait for Dapr readiness

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.