Tracking issue - Multi-app run enhancements

[mukundansundar]

Describe the proposal

• [x] https://github.com/dapr/cli/issues/1220
• [x] https://github.com/dapr/cli/issues/1221
• [x] https://github.com/dapr/cli/issues/1228
• [x] https://github.com/dapr/cli/issues/1204
• [ ] https://github.com/dapr/cli/issues/1144
• [ ] https://github.com/dapr/cli/issues/1145
• [ ] https://github.com/dapr/cli/issues/1146
• [ ] https://github.com/dapr/cli/issues/1147
• [x] https://github.com/dapr/cli/issues/1154
• [ ] https://github.com/dapr/cli/issues/1155

Release Note

RELEASE NOTE:

[mcrio]

Hi @mukundansundar I wasn't aware of this topic so copying my comment from another one which is closed in favor of this one:

First I would like to thank the contributor for providing this feature :)

Use case: Start multiple .net based services and their Dapr sidecars during development. Previously I used Tye (no longer maintained).

What I like so far:

• Faster startup time compared to Tye
• Easy Yaml config

What I am having some difficulties with:

• After running dapr run in case some service fails to start that is not indicated in the CLI output.
• Logs have a hard coded path, namely the projects .dapr/logs subdirectory.
• It's not very easy to hunt for the logs in different folders and files, especially as each run generates new files.