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 44a48f56d fix(doc): more 404 links
44a48f56d is described below
commit 44a48f56d9aec199084ee4c5030cbd0de9ec9ff7
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Thu Sep 19 15:58:11 2024 +0200
fix(doc): more 404 links
---
addons/keda/keda.go | 2 +-
docs/modules/ROOT/pages/troubleshooting/debugging.adoc | 2 +-
docs/modules/traits/pages/keda.adoc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/addons/keda/keda.go b/addons/keda/keda.go
index d4fb3816a..1c7ff2b56 100644
--- a/addons/keda/keda.go
+++ b/addons/keda/keda.go
@@ -66,7 +66,7 @@ const (
// via markers in the Kamelets.
//
// For information on how to use KEDA enabled Kamelets with the KEDA trait,
refer to
-// xref:ROOT:kamelets/kamelets-user.adoc#kamelet-keda-user[the KEDA section in
the Kamelets user guide].
+// xref:ROOT:pipes/pipes.adoc#kamelet-keda-user[the KEDA section in the Pipes
user guide].
// If you want to create Kamelets that contain KEDA metadata, refer to
// xref:ROOT:kamelets/keda.adoc[the KEDA section in the Kamelets development
guide].
//
diff --git a/docs/modules/ROOT/pages/troubleshooting/debugging.adoc
b/docs/modules/ROOT/pages/troubleshooting/debugging.adoc
index b7901bf53..6e685b0e4 100644
--- a/docs/modules/ROOT/pages/troubleshooting/debugging.adoc
+++ b/docs/modules/ROOT/pages/troubleshooting/debugging.adoc
@@ -57,6 +57,6 @@ When the debugging session is done, hitting kbd:[Ctrl+c] on
the terminal where t
As we've seen in the previous section, all `Integration` created in Camel K
are finally bundled as a Java application, hence, the possibility to debug via
JVM debugger. Any `Kamelet` you will be using directly in your `Route`
definition or in a `Pipe` is automatically converted in a `yaml` route and
injected in the Camel Context to be executed. That means that you cannot
directly debug a `Kamelet` as you would do with a Java or any other JVM
language `Route`.
-However, you can troubleshoot individually each `Kamelet` definition by
focusing on the specification xref:kamelets/kamelets-user.adoc#_flow[`Flow`].
As an example, you can create a simple `yaml` test `Route` substituting the
`kamelet:source` or `kamelet:sink` with any mock endpoint that can help you in
debugging the single `Kamelet` flow. Even using a `timer` and a `log` component
may be enough for a basic check.
+However, you can troubleshoot individually each `Kamelet` definition by
focusing on the specification `Flow`. As an example, you can create a simple
`yaml` test `Route` substituting the `kamelet:source` or `kamelet:sink` with
any mock endpoint that can help you in debugging the single `Kamelet` flow.
Even using a `timer` and a `log` component may be enough for a basic check.
NOTE: the same idea applies for a `Pipe` which translates to an `Integration`
type under the hood. If you need to debug a `Pipe` just apply the same
troubleshooting technique that you would apply on an `Integration`.
diff --git a/docs/modules/traits/pages/keda.adoc
b/docs/modules/traits/pages/keda.adoc
index 0ecaf9c93..c198016e8 100644
--- a/docs/modules/traits/pages/keda.adoc
+++ b/docs/modules/traits/pages/keda.adoc
@@ -8,7 +8,7 @@ The trait can be either manually configured using the
`triggers` option or autom
via markers in the Kamelets.
For information on how to use KEDA enabled Kamelets with the KEDA trait, refer
to
-xref:ROOT:kamelets/kamelets-user.adoc#kamelet-keda-user[the KEDA section in
the Kamelets user guide].
+xref:ROOT:pipes/pipes.adoc#kamelet-keda-user[the KEDA section in the Pipes
user guide].
If you want to create Kamelets that contain KEDA metadata, refer to
xref:ROOT:kamelets/keda.adoc[the KEDA section in the Kamelets development
guide].
