squakez commented on PR #4021: URL: https://github.com/apache/camel-k/pull/4021#issuecomment-1413418078
As I'm working on some ideas around Camel K 2.0 (gitops, being able to build _any_ Camel application, ...), let me share with you something I've been thinking lately. I may probably create an issue with some visual support, but hopefully can help you in the work you're doing. I think that instead of passing the whole content of a source along the different CRs, we should have the concept of a "generated Maven project" (it may even come from `camel export` - Camel JBang instead of our own logic). This is a standard Maven project that could be even stored in a Git repository. The project should be generated by the Operator when an Integration is submitted (here we can think to provide the Source or the Git repo URL). In the first case a _project generation_ is triggered (ie, via Camel JBang) and we should store temporary the result in a workspace directory. The project generation may be controlled via a new Custom Resource and a reconciliation loop. Once the Project is `ready`, the Build can kick off. The Build has to be fed with the workspace directory and the rest should be proceeding more or less the same way it is now (in order to be able to reuse the incremental image kit 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
