Ability to start a resource that failed to start (e.g. a dependency load failure)

What do you mean by this? I believe FailedToStart state resources can already be started.

The RuntimeUnhealthy can't be explicitly started from that state right now. Do you want it changed to allow the start command?

@karolz-ms Is there a situation where someone would want to be able to expliclty start a container via a resource command when the container is in a RuntimeUnhealthy state? I tested it out, and nothing happened, which is what I expected.

This is about refactoring the code in application executor so that commands can restart the entire workflow in the apphost and not just call dcp

@karolz-ms Is there a situation where someone would want to be able to expliclty start a container via a resource command when the container is in a RuntimeUnhealthy state? I tested it out, and nothing happened, which is what I expected.

The RuntimeUnhealthy is a transient state for a container that is otherwise within the startup sequence (which includes building/fetching an image, creating, connecting to networks, and actual start, as necessary). It will be started automatically once the runtime becomes healthy again. So there is really no point in starting it manually, it won't change anything really.