microsoft / microsoft/aspire

Can't force start a resource for a second time

Open
#14,812 1 comment 0 reactions 0 assignees View on GitHub
area-app-model area-dashboard
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

### Is there an existing issue for this?

- [x] 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

1. Start the below app host. Notice that the `blockee` resource is in the `Waiting` state
2. Start the `blockee` resource - it force starts as expected
3. Wait for the `blockee` resource to complete
4. Start the `blockee` resource again, it now transitions into the `Waiting` state

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.

```cs
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_

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.