Skip to content
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

Custom Component json to kamelet yaml #1741

Closed
skumaravelan opened this issue Nov 16, 2023 · 6 comments
Closed

Custom Component json to kamelet yaml #1741

skumaravelan opened this issue Nov 16, 2023 · 6 comments

Comments

@skumaravelan
Copy link

For custom component services, we have written components.json file and and have corresponding classes in the camel runtime to execute the integrations . I am trying to figure out a mechanism of using the custom components.json file, i would like to define an kamelet.yaml using any pre existing tools by camel. so that we can use those tools to convert to kamelet file and update as needed using a Karavan kind of visual tool. I understand that these are two different ways of executing the components. As Karavan supports kamelet it works elegantly when we have these files converted using a camel cli or something along those line. Any suggestion on this front would help.

@oscerd
Copy link
Contributor

oscerd commented Nov 17, 2023

Kamelets expects the components to be in the camel catalog. So it's not possible as of today to use directly a custom component through them.

@skumaravelan
Copy link
Author

Is there a bootstrap utility program to convert json to kanelet.

@oscerd
Copy link
Contributor

oscerd commented Nov 17, 2023

No, there isn't. But if you're take into consideration custom component, even if you would be able to convert from json to Kamelets, the Kamelets wouldn't work.

@skumaravelan
Copy link
Author

What are the consideration and requires to work?

@oscerd
Copy link
Contributor

oscerd commented Nov 17, 2023

The requirements would be to support a custom catalog, but this is not related to Kamelets, it's something more general @davsclaus

@oscerd
Copy link
Contributor

oscerd commented Nov 24, 2023

Going to close this, since it's not on the roadmap and it's not related to this repository

@oscerd oscerd closed this as not planned Won't fix, can't repro, duplicate, stale Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants