-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MongoDB sink: error during trait customization: component not found for uri #4058
Comments
@squakez as far as I remember this always worked in this way. Do you have any clue? I'll try to reproduce btw |
There are multiple kamelets using that approach. I think this is important to fix for 1.12.0. Let me add it to the list. |
Yes, thanks @christophd , it seems it will be fixed in 1.12. I wonder if it makes sense to backport to 1.11 and 1.10 branches as well, as it looks to be failing on those versions as well. Do you think you can have a look? |
Probably it doesn't make sense to do it on 1.11. It's not an LTS, we released 1.11.1 just for OpenJDK troubles |
This should be fixed with 1.12.0 just released. @fourstepper can you please have a look and confirm if it now works? |
Hi @squakez , I can confirm that this works now, thank you! I will therefore close this issue |
Hi, I am having issues setting up the MongoDB sink using the included kamelet
I am trying to set up a mongoDB sink with RMQ source using a kameletbinding after installing the
camel-k operator 1.11.x
This issue was also discussed on Zulip here
My full configuration is:
This throws the following error in the KameletBindings' status that leaves me a bit puzzled and stuck:
This is probably somehow related to this line, but I still don't have many ideas on how to fix the issue https://github.com/apache/camel-kamelets/blob/main/kamelets/mongodb-sink.kamelet.yaml#L106
This isn't even mentioned in the docs anywhere and I am using the stock Kamelet that comes with the operator when installing it using the helm-chart
The text was updated successfully, but these errors were encountered: