Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
13.3 has added a new State detail property. It would be really helpful if this explicitly stated which remaining resources.
Describe the solution you'd like
Whilst you can reverse engineer this from the console logs of your resource, it would be a lot easier if something could explicitly highlight which remaining resources are blocking.
Bonus points if the list of remaining dependencies could be built into the wait timeout errors built in BuildCancellationErrorMessage inside ResourceNotificationService
Additional context
#:sdk Aspire.AppHost.Sdk@13.3.0
var builder = DistributedApplication.CreateBuilder(args);
var a = builder.AddContainer("nginx", "nginx").WithExplicitStart();
var b = builder.AddContainer("nginx2", "nginx").WaitFor(a);
builder.Build().Run();
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
13.3 has added a new
State detailproperty. It would be really helpful if this explicitly stated which remaining resources.Describe the solution you'd like
Whilst you can reverse engineer this from the console logs of your resource, it would be a lot easier if something could explicitly highlight which remaining resources are blocking.
Bonus points if the list of remaining dependencies could be built into the wait timeout errors built in
BuildCancellationErrorMessageinsideResourceNotificationServiceAdditional context