[GitHub] [camel-k] bfitzpat opened a new issue #938: Kamel cli should send exit code when integration in --dev mode is deleted

[GitBox <gi...@apache.org>]

bfitzpat opened a new issue #938: Kamel cli should send exit code when integration in --dev mode is deleted
URL: https://github.com/apache/camel-k/issues/938
 
 
   In the tooling I'm having some difficulty finding ways to kill a --dev mode integration effectively. 
   
   Essentially we're using Node.js child_process calls to spawn a cli call (i.e. kamel run "myintegration.groovy" --dev) and then we're listening for console output and bouncing that to a VS Code output channel. The problem is we don't have a clear signal to say that the --dev mode session is finished. We can't exactly do a Ctrl+C to stop the kamel --dev session from inside the tooling (though I am trying to find a way to replicate that). 
   
   It looks like we're getting an exit signal on an error - https://github.com/apache/camel-k/blob/97d8d726d5543f501afb6bd8901345b3127f09ad/cmd/kamel/main.go#L47 so it seems we are sending a code on exit in some places (like when an integration stops - https://github.com/apache/camel-k/blob/97d8d726d5543f501afb6bd8901345b3127f09ad/pkg/cmd/run.go#L195)
   
   Because of this, we're running a kamel --dev integration and then removing it with kamel delete. But that's not ever killing our initial kamel session - we're not getting a close or exit signal that says that it's done. 
   
   Is there any chance that the kamel cli can send that exit/close signal when a --dev integration is deleted? I know it's a bit of an edge case, but it would help us out in the tooling.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services