ReggieCarey commented on issue #673: URL: https://github.com/apache/camel-kamelets/issues/673#issuecomment-1006988572
I have been a huge fan and promoter of Camel-K since I discovered it approximately 1 year ago. It's a very useful tool and can dramatically reduce large system complexity. I'm more than aware of the alpha / pre-alpha quality of some of the components. As such, I've tried to work around the various shortcomings without filing bugs. @oscerd thank you for making this repair. When the community says the documentation useless, don't take offense, sometimes the truth hurts. Take it as an opportunity to make things clearer for the community. The documentation around KameletBindings as described in the Kamelet Catalog fails to provide sufficient detail to use the software effectively. I hope I provided some suggestions that clarify what these actions do so that it's not so confusing to others. The Open Source developers have a dramatically better insight into what's going on under the hood. As consumers of the solution, we often do not have insight into the inner workings of the code. This makes it impossible to provide constructive feedback. Many users of this technology have no Java background and digging through code ends up being a fruitless effort for them. The only recourse is to file a bug/open an issue. I've been working this problem for at least 6 months and have consumed 100's of hours of time and resources on this. Feedback in this issue chain helped me find the code that lead to better understanding of what these actions are doing. I hope my comments and suggestions lead to updated documentation and code that is better for all who wish to use this open source product. By the way: If you're not already aware. All of the links in the Kamelet Catalog that point to the Kamelet Source Files are broken and lead to a 404 on GitHub. On a personal note: I wish you had responded with this latest bit of information about a fix 20 hours ago instead of waiting for me to discover the same or similar solution before telling us that there is already a solution developed 17 days ago. I was busy trying to find a solution based on combining and working with actions documented in the Kamelet Catalog. Now I know, having read some of the code, that there is likely no solution to the problem by attempting to manipulate the configuration of one or more actions in a kameletbinding. -- 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
