oscerd commented on issue #1244: URL: https://github.com/apache/camel-kamelets/issues/1244#issuecomment-1398049007
To me, it's almost impossible to accomplish this, for multiple reasons: - We give the opportunity to write a Kamelet in multiple ways (like having toD, to and some steps in between) - We provide a basic catalog that could be extended as users wish In my opinion we don't really need a way to extend a single kamelets, but we might need to create a way of having some kind of Kamelets marketplace (like for example ansible galay or Terraform modules). In that way anyone could take kamelets, extend them and eventually publish their own catalog in the marketplace. Even our catalog could be improved, for example through the addition of other labels like "Advanced", "Beginner", "Ready for Prod" etc. I think we should focus more on supporting different catalogs in all the runtimes, than on extending the single Kamelet. It's a tradeoff, but I do think the advantages will be more if we think about Kamelets like a catalogs marketplace. -- 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
