Dapr sidecar WaitFor

[bgelens]

Related to an existing integration?

Yes

Existing integration

CommunityToolkit.Aspire.Hosting.Dapr

Overview

The dapr sidecar will start immediately while the redis container supporting pubsub for example is still starting.

The application has a WaitFor configured but the sidecar will fail the on pubsub component loading as redis is not done starting. When redis is started, the application will start and then fail because the sidecar has failed.

Usage example

To make this play more nicely, the sidecar starting should either respect the application WaitFor configuration or be expanded to have its own.

additionally, I'm running the dapr scheduler and placement services using the dapr container images as well. Using this scenario, it would make more sense to have an additional WaitFor configuration on the sidecar configuration.

Breaking change?

I'm not sure

Alternatives

use persistent container runs and restart aspire host

Additional context

No response

Help us help you

No, just wanted to propose this

[github-actions]

We have noticed this issue has not been updated within 21 days. If there is no action on this issue in the next 14 days, we will automatically close it. You can use /stale-extend to extend the window.

[bgelens]

/stale-extend