-
Notifications
You must be signed in to change notification settings - Fork 813
Open
Labels
area-app-modelIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplicationIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
When you first start your app host, aspire lets you Start a resource that is waiting to force it to start, even if it is waiting for dependencies.
If however you stop and then start the resource again, the force start options disappears.
Expected Behavior
I should be able to force start resources on subsequent runs.
Steps To Reproduce
- Start the below app host. Notice that the
blockeeresource is in theWaitingstate - Start the
blockeeresource - it force starts as expected - Wait for the
blockeeresource to complete - Start the
blockeeresource again, it now transitions into theWaitingstate
I'd expect to be able to press Start again to force start blockee a second time, but the option is greyed out so I can't.
var blocker = builder.AddExecutable("blocker", "pwsh", ".")
.WithExplicitStart();
var blockee = builder.AddExecutable("blockee", "pwsh", ".")
.WaitFor(blocker);Exceptions (if any)
No response
.NET Version info
No response
Anything else?
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area-app-modelIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplicationIssues pertaining to the APIs in Aspire.Hosting, e.g. DistributedApplication