-
Notifications
You must be signed in to change notification settings - Fork 71
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
Kamelet with id aws-s3-source not found in locations: file:/etc/camel/kamelets/kamelets-bundle-aws-s3-source-pipe-001,classpath:/kamelets #1785
Comments
You need to set the region too, if you set accessKey and secretKey
It's reported in the error: |
yeah, I just realized that too. Thanks! After adding the
which reminds me of #1777 |
yes, it's the same situation. |
OK, than I am blocked. Anyways, thanks for the help on both tickets. |
I hope we are able to release camel-k 2.2.0 soon @squakez |
What I also do not fully like, is that the
While in the pod has an exception and it could be set to |
This should go in the camel-k repository as issue I guess. |
ok! will do |
Yeah, more than on Camel K this depends on the runtime. I'm planning to cut a release for both during next weeks. Keep tuned. |
@matzew here is one thing that you can try to unblock this until the new release is available. Go to and apply this Kamelet to your local user namespace (where you run the Pipe): Or overwrite the aws-s3-source Kamelet in the operator namespace with this. This points to the Kamelet utils library version 4.1.0 which should have the data type available. Please let me know if this works. |
They both run in |
Turns out this is related to camel-k#5047 because service discovery mechanism for data types has been broken. Fixed with camel-k#5055 |
Now trying the
aws-s3-source
Kamelet
, it looks like:However, in the pod for that "aws source" I get the following
But the
kamelet
is there:I install Camel-K on Minikube, via https://github.com/matzew/eventing-cloud-integration/tree/main/system
The text was updated successfully, but these errors were encountered: