Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

A command to start/stop/restart a resource involves:

1. Dashboard sending command to the app host. For example, a command to stop a resource.
2. App host sends a request to DCP to perform an action.
3. DCP queues this action and then returns back to the app host.
4. App host returns back to the dashboard that there was a success.

The problem is the app host doesn't wait for the resource to actually change to the desired state before returning a response to the dashboard. The resource could still be stopping and stop after the dashboard reports success. Or the resource might not be stopped because of a problem inside DCP, but the dashbaord has already reported success.

Describe the solution you'd like

The app host waits for a resource to enter the desired state before returning a success/fail result to the dashboard.

If starting a resource fails, that's reported as a failure to the dashboard.
If something hangs, then after a timeout (20 seconds?) that's reported as a timeout to the dashboard.

Additional context

No response