This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/main by this push:
new 6a41a359c fix(doc): kamelet distribution instructions
6a41a359c is described below
commit 6a41a359c2f432359bad3aa4b91f95e9e1e58e02
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Thu Nov 28 18:30:09 2024 +0100
fix(doc): kamelet distribution instructions
Closes #5958
---
docs/modules/ROOT/pages/kamelets/kamelets-distribution.adoc | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/docs/modules/ROOT/pages/kamelets/kamelets-distribution.adoc
b/docs/modules/ROOT/pages/kamelets/kamelets-distribution.adoc
index 77e5a99fb..a2e9f0e5e 100644
--- a/docs/modules/ROOT/pages/kamelets/kamelets-distribution.adoc
+++ b/docs/modules/ROOT/pages/kamelets/kamelets-distribution.adoc
@@ -12,9 +12,11 @@ As development of Kamelet is very fast, make sure to use
some version which is c
An alternative to the catalog we bundle is to include a repository containing
your own catalog. You need to specify it in the IntegrationPlatform
`.spec.kamelet.repository`.
-However, we have a simple command in our CLI which takes care of it:
-```
-kamel kamelet add-repo
<git-platform>:<owner>/<repo>[/path_to_kamelets_folder][@version]
+```yaml
+ spec:
+ kamelet:
+ repositories:
+ - uri: <git-platform>:<owner>/<repo>[/path_to_kamelets_folder][@version]
```
Mind that `<git-platform>` is the repository of your choice, for instance
`github` and `[@version]` is the tag to use (by default it will use `main`
branch).
@@ -27,4 +29,4 @@ The Camel K has an opinionated way to use Kamelets which is
the one exposed abov
However, you may find situations where you want to bundle a Kamelet in a
dependency (ie, some external catalog containing all Kamelets spec). As
Kamelets are a Camel thing, then, you can use such dependency and let the
runtime use the Kamelets available in the classpath.
-If you're using such an approach, then, you will need to make sure to skip the
Kamelet trait (which is in charge to discover them and get required
dependencies), and provide all the dependencies which may be required by your
Kamelet. Additionally, you may need to specify a Camel property to tell the
runtime where to expect to find the Kamelets,
`camel.component.kamelet.location` (default `classpath:/kamelets`).
\ No newline at end of file
+If you're using such an approach, then, you will need to make sure to skip the
Kamelet trait (which is in charge to discover them and get required
dependencies), and provide all the dependencies which may be required by your
Kamelet. Additionally, you may need to specify a Camel property to tell the
runtime where to expect to find the Kamelets,
`camel.component.kamelet.location` (default `classpath:/kamelets`).
