knockknock10 commented on PR #6917: URL: https://github.com/apache/camel-k/pull/6917#issuecomment-6462774458
Thanks, @squakez! That makes sense — supporting only catalog Kamelets would create an inconsistent experience for users. I’ve removed that path in `aad0e31` and kept the proposal focused on statically available Integration/component properties. I’d be interested in your thoughts on the next step: would it make more sense to first settle the mapper-input and property-precedence design around #6893, or is there another part of this problem you think deserves attention? -- 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]
