Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add capability for dapr run -f to start apps in parallel #1174

Open
mukundansundar opened this issue Jan 20, 2023 · 4 comments
Open

Add capability for dapr run -f to start apps in parallel #1174

mukundansundar opened this issue Jan 20, 2023 · 4 comments
Labels
kind/enhancement enhancement to an existing feature pinned

Comments

@mukundansundar
Copy link
Collaborator

Describe the proposal

This issue is a follow up on the comment in PR #1161.
Currently dapr run -f starts the apps in series one after the other and that might not be the preferable option for users.
We need to parallelize the app starts.
Additional features that should be added are a delay field to delay the starting of the app after the previous app has been started. As well as a feature dependsOn, if some app is dependent on another app starting up first.

cc @philliphoff
related to #1123

Release Note

RELEASE NOTE:

@mukundansundar mukundansundar added the kind/enhancement enhancement to an existing feature label Jan 20, 2023
@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement enhancement to an existing feature pinned
Projects
None yet
Development

No branches or pull requests

2 participants