-
Notifications
You must be signed in to change notification settings - Fork 18
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
Allow killing Dapr applications #81
Comments
DescriptionBackgroundCurrently there is no way to kill a Dapr application detected from the UI found in the VS Code extension. Users would have to either kill the debugging process started that has initiated the Dapr application or kill the application from what ever terminal it has been started. RequestAdd a command that kills a specific Dapr application when that application is selected. This command should be a right click command option that only effects the selected Dapr application. Mockup |
* added stop app command and documentation * updated stop app to use process wrapper * removed comments and temp bug fix for dapr list error * added stop app assets * removed unused imports and fixed eslint errors * minor changes to var names * updated stop application to kill instances of dapr and daprd * windows support + minor refactoring * updating package-lock * changed kill proc to SIGTERM * updated to use which module to find daprd executable * adding package.json * updated package-lock * removed unused imports * updated error handling * moved stop logic to dapr cli client * added open telemetry module
Add an option to kill a running Dapr application (i.e. its
dapr
ordaprd
instance) from the Dapr applications tree view. If the application does not shut down nominally after debugging, it's not always obvious how/where to stop it so that the user can restart without fear of strange conflicts. (Especially since thedapr
CLI does not show arbitrarily starteddaprd
instances.)The applications tree view could offer a "kill" context menu command (at least for instances that it, itself, started) to allow for quick, forced shutdowns and restarts.
The text was updated successfully, but these errors were encountered: