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

Kamelet Catalog as Maven dependency #165

Closed
assimbly opened this issue Apr 23, 2021 · 4 comments
Closed

Kamelet Catalog as Maven dependency #165

assimbly opened this issue Apr 23, 2021 · 4 comments
Assignees

Comments

@assimbly
Copy link

Topic: Kamelet Catalog

Functionality: As developer I would like to access the Kamelet Catalog programmaticly

Background:

Currently, the Camel catalog is already available as Maven dependency (jar file):

https://mvnrepository.com/artifact/org.apache.camel/camel-catalog

Most information in the Camel catalog (https://camel.apache.org/manual/latest/camel-catalog.html) is available through a JSON Schema. Similar layout/schemas would be preferable for the Kamelet catalog as this is corresponds to the way Camel developers are used to. Somethings however maybe better in a format like YAML. The Camel catalog makes it possible to get information about for example a component from within a program.

I would like the same for the Kamelet Catalog (https://camel.apache.org/camel-kamelets/latest/). In this way developers can access a list of available Kamelets and for a specific Kamelet get information about the version/documentation/configuration(yaml)/dependencies and so on.

Ideally the Kamelet Catalog can also be used to load a Kamelet within a Camel runtime. (This would be a use case for Asismbly or other low-code platforms like Syndesis).

@oscerd oscerd self-assigned this Apr 26, 2021
@oscerd
Copy link
Contributor

oscerd commented Apr 26, 2021

I'm starting working on this.

@oscerd
Copy link
Contributor

oscerd commented Apr 27, 2021

@apupier
Copy link
Contributor

apupier commented May 3, 2021

@oscerd
Copy link
Contributor

oscerd commented May 4, 2021

This is implemented now. Let's open other issues for improvements and more.

@oscerd oscerd closed this as completed May 4, 2021
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