christophd commented on PR #12474: URL: https://github.com/apache/camel/pull/12474#issuecomment-1864506435
> 1. It would be great to have jbang with a plugin for different command sets, as we end up with a big pile of dependencies and many commands that will get us in trouble in the future. Good to hear you do some experiment with this. Its not only the CK stuff that we can separate. It would also be for example the generator command, sbom, jolokia, hawtio etc Working and experimenting on it but it will take some more time to get results > 3. the get command has been called get for all its life in camel-k, and we use same name in camel-jbang, so I think its not a good idea to rename it to list (old habbits die hard) I'll go back to `camel k get` and push to this PR > 4. docs, the jbang docs is a very long page, it needs to be broken up into sub pages, so a good start is to have the CK in its own sub page. And then we can use that as starting point to break up the existing big page also. Working on it and will push to this PR > 5. can the tests run in isolation or do they need a running k8s cluster. Just want to sure that we can build everyhing nicely without causing test failures due to k8s stuff as core project dont have any of that. Yes, the Kubernetes mockserver used in the tests is just an arbitrary Http server that emulates the Kubernetes API. No need to have a Kubernetes cluster > 6. mind that jbang is for developers and not sys admins, or ops guys. I think the kubectl, oc and kamel go cli would be needed for those guys - I cant see them want to install java jbang to run a shell command. Right, and we should always provide the opportunity to use these standard tooling for instance by doing the pipe to `kubectl` as Pasquale suggested. At the same time I think Camel JBang is a great way to start with Camel and it should also be a great way to start with integrations running on Kubernetes. -- 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. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
