Log container to STDOUT + List and Stop running services

[Croway]

• Use ~/.camel to handle running infra service processes, the infra process start with infra- and have the following structure infra-{serviceName}-{pid}.log
• Add camel-test-infra-common to camel-jbang-core, this will add testcontainer as a dependency, @davsclaus is it doable? otherwise, I'll refactor the code to use reflection heavily. If you do not see an issue having testcontainer as dependency in camel-jbang-core, I'd move CamelLogConsumer into camel-jbang-core
• By default the log file will contain the container log, I added a flag --log that output the log to the stdout.
• Added a stop command, can be used like camel infra stop minio that will delete the file and kill the process (@davsclaus I used a slightly different approach compared to StopProcess).
• Added a --running parameter to the list command that shows only the running services

$ camel infra run minio
Starting service minio
{
  "accessKey" : "testAccessKey",
  "host" : "localhost",
  "port" : 32835,
  "secretKey" : "testSecretKey"
}
Press any key to stop the execution

$ camel infra list --running
 ALIAS             IMPLEMENTATION  DESCRIPTION
 minio                             MinIO Object Storage, S3 compatible
 
$ camel infra stop minio
Shutting down service minio (PID: 28844)

I'd remove the log Press any key to stop the execution since infra stop is implemented, wdyt?

[davsclaus]

Maybe use ps or get as we do for camel

camel infra ps

Show just some basic information

camel infra get

Should more details

Then its the same as for camel run

[davsclaus]

Does this give test container time to stop the service cleanly, as if you destroy the pid by force then would that not be something like kill -9 ?

[davsclaus]

Yeah we need to not have this dependency.

You can dynamic download this JAR via that camel maven thing, and we can maybe try set its scope = provided so camel run will not use it normally. And then you can still compile and use its API just that you have downloaded the JAR first.

Otherwise we can also move the command to its own camel jbnag plugin then the dependency can be there (just k8s has kube client JAR etc). But then users need to install this plugin first before they can use it.