mertdotcc commented on issue #4126: URL: https://github.com/apache/camel-k/issues/4126#issuecomment-1477735563
Thanks for digging into the issue @squakez! > Use a build time properties that everytime is different. I have one handy for this case `kamel run --build-property=quarkus.application.name=integrationTwo`. We want to avoid this as much as possible since we want to stick to our strict naming conventions and not keen on the manual work of using a different build-time property for each run. > Designing the route not to depend on a specific resource path could be a solution for now. I agree, this is something that I will try. I'll also explore the generic file approach you mentioned [here](https://github.com/apache/camel-k/issues/4126#issuecomment-1465738335). For the time being, would something like this be possible: I deploy my `IntegrationOne`, the operator builds the native image, `IntegrationOne` gets deployed using the image, all fine. Then I deploy my `IntegrationTwo`, it uses the native image built for `IntegrationOne` since they share a lot of logic, but detects that my `IntegrationTwo` uses a resource file that is not present in the image built for `IntegrationOne`, and then builds a new image that contains the first image, and just adds the missing resource file on top as a new layer? So that we could avoid another costly and timely native image build process, and stick to Camel-K's efficient image re-use and layering logic? -- 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
