`WithDaprSidecar` doesn't mimic `WaitFor` on its parent resource

[atrauzzi]

Describe the bug

Whenever I call WithDaprSidecar on a resource that has a WaitFor, the sidecar always starts immediately.

Regression

No response

Steps to reproduce

Make one resource that uses a Dapr sidecar wait on another.

Expected behavior

Whenever I call WithDaprSidecar on a resource, I'd expect it to mimic any WaitFor instructions made against its parent.

Screenshots

No response

IDE and version

Rider

IDE version

No response

Nuget packages

Latest

Additional context

No response

Help us help you

Yes, but only if others can assist

[kristremblay]

I am facing the same issue. Latest version of everything, .net 10, MacOS.

The hacky way I was able to use to get it to work the way I expected: drop the WithDaprSidecar call and instead write an executable that prefaces the dapr command with a sleep.

var api = builder.AddProject<Projects.PropertyManager_Api>("api")
    .WithReference(db)
    .WithReference(rabbitMq)
    .WaitFor(postgres)
    .WaitFor(rabbitMq);

builder.AddExecutable(
        "api-dapr-sidecar",
        "bash",
        args:
        [
            "-c",
            "sleep 30 && dapr run --app-id api --app-port 5225 --dapr-http-port 3500 --dapr-grpc-port 3501 --resources-path ../components/ --config ../components/dapr-config.yaml --log-level debug"
        ],
        workingDirectory: ".")
    .WaitFor(api);