lburgazzoli commented on issue #1821: URL: https://github.com/apache/camel-k/issues/1821#issuecomment-731604664
This is actually not accurate, we need the route as it is what drives the materialization of various aspects of the integration but we actually recommend providing additional logic through artifacts On Sat, 21 Nov 2020 at 17:33, Zoran Regvart <[email protected]> wrote: > I think the biggest drawback of Camel K being able to address moderate to > high complexity cases is in it's over-reliance on having to fit the whole > implementation of the solution in the CR. I think Camel K should consider > supporting container images or archives instead. So instead of putting the > code into a CR, I as a developer, should be able to push an image/archive > with the code instead, have the operator integrate it into an runnable > image. > > — > You are receiving this because you commented. > > > Reply to this email directly, view it on GitHub > <https://github.com/apache/camel-k/issues/1821#issuecomment-731602081>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAOIJBIOI6B3WMUSLZ5IGNTSQ7TVLANCNFSM4T5CPGOA> > . > -- -- Luca Burgazzoli ---------------------------------------------------------------- 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: [email protected]
