You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of today, Karavan only supports specifying a custom Kamelets location as a local file system path. This is inconvenient for teams that want to share and reuse Kamelets, which is their main purpose.
Karavan in VS Code should be able to display and retrieve a catalog of Kamelets from a remote location, such as a Git repository (like github:apache:camel-kamelets/kamelets) or a Maven repository (included in a jar dependency like org.apache.camel.kamelets:camel-kamelets-catalog).
The repositories may need private access, like credentials and/or private keys.
This way, it will be possible to create Kamelets and share them privately in a company.
Currently, the suggested solution is to clone a git repository in a local filesystem path and configure the Karavan VS Code extension to use this path (link).
The text was updated successfully, but these errors were encountered:
We encountered the same issue as you did, and we plan to use an HTTP interface to read Kamelets. Additionally, we are designing a new page specifically for managing all custom Kamelets and persisting the text of Kamelets to the database.
As of today, Karavan only supports specifying a custom Kamelets location as a local file system path. This is inconvenient for teams that want to share and reuse Kamelets, which is their main purpose.
Karavan in VS Code should be able to display and retrieve a catalog of Kamelets from a remote location, such as a Git repository (like
github:apache:camel-kamelets/kamelets
) or a Maven repository (included in a jar dependency likeorg.apache.camel.kamelets:camel-kamelets-catalog
).The repositories may need private access, like credentials and/or private keys.
This way, it will be possible to create Kamelets and share them privately in a company.
Currently, the suggested solution is to clone a git repository in a local filesystem path and configure the Karavan VS Code extension to use this path (link).
The text was updated successfully, but these errors were encountered: