lburgazzoli commented on issue #4166: URL: https://github.com/apache/camel-k/issues/4166#issuecomment-1558592505
I'm not sure we should use properties as it seems a little bit confusing to me, as example, if you want to configure something related to the memory consumed by a pod, then using a property seems to be misleading as that's usually something you pass to the runtime. It will also leak some property to the user which may them rely on them which would increase our maintenance cost. In some of the previous conversation we had, we discussed: - camel-k to define a contract with the runtime which could be a simple set of properties that are set by camel-k for a specific feature, but such properties are not supposed to be used by or exposed to users directly - the runtime part to implement the required machinery to fulfill the contract when possible in the form of a camel quarkus extension or spring boot starter or something else in the future - the runtime to provide its catalog and related capabilities (which only require to define if it is available and what are the related dependencies) - the runtime to provide its building tools/image (i.e. as part of the info present in the catalog) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
