doru1004 commented on pull request #1816: URL: https://github.com/apache/camel-k/pull/1816#issuecomment-763885570
Just to clarify, Inspect is always local, and local means local to where the kamel executable is being invoked. So if you run kamel inspect on your machine then the local environment is that machine, if you run inspect in a cloud environment or container then the local environment is that cloud environment or container. What inspect does not do when you run it on your machine is give you information about the dependencies in the cloud (which is what I would think hybrid means). Regarding `kamel local build`, I think that's definitely a possibility but `kamel local build` would have to do much more than `kamel inspect` currently does. The output of `kamel local build` must be something that can be run by invoking `kamel local run` on it. The closest we have today to `kamel local build` is `kamel local create` which takes the integration files, creates a container and builds it into a docker image that can be passed to `kamel local run`. We could rename `local create` to `local build` and add the capability to output something for when the command does not output an image. This something would have to be a local directory structure containing all the integration files: dependencies, property files and route files that define the integration. This is needed because we can then pass this directory structure to `kamel local run` to run the integration. ---------------------------------------------------------------- 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: us...@infra.apache.org
