This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 1da430ea812d chore: docs - use relative links to the blog in the
Governed AI Agents page (#28587)
1da430ea812d is described below
commit 1da430ea812dde4cdb4dd45b94fbbb8cf3ba5a80
Author: Federico Mariani <[email protected]>
AuthorDate: Tue Oct 27 19:54:03 2026 +0100
chore: docs - use relative links to the blog in the Governed AI Agents page
(#28587)
The website HTML check (camel/relative-links) rejects absolute links to
camel.apache.org, which fails every camel-website pull request build.
---
docs/user-manual/modules/ROOT/pages/governed-ai-agents.adoc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/governed-ai-agents.adoc
b/docs/user-manual/modules/ROOT/pages/governed-ai-agents.adoc
index d8b9b16e5b98..43995f008411 100644
--- a/docs/user-manual/modules/ROOT/pages/governed-ai-agents.adoc
+++ b/docs/user-manual/modules/ROOT/pages/governed-ai-agents.adoc
@@ -325,10 +325,10 @@ together: the proxy governs at the perimeter, and the
route still checks the cal
*
https://github.com/apache/camel-examples/tree/main/ai-tools-spiffe-opa[ai-tools-spiffe-opa
example]: a support
assistant with three tools, two callers with SPIFFE identities and an OPA
WebAssembly policy, all with Docker
Compose.
-* https://camel.apache.org/blog/2026/09/securing-ai-agent-tools/[Authorizing
what an AI agent may do in Apache Camel]
-*
https://camel.apache.org/blog/2026/09/camel-spiffe-workload-identity/[Workload
identity in Apache Camel with SPIFFE and SPIRE]
-*
https://camel.apache.org/blog/2026/09/semantic-evaluation-system-one/[TypeSafe
Jev meets Apache Camel: semantic decisions in Camel routes]
-* https://camel.apache.org/blog/2026/10/semantic-agent-routing/[One request,
several agents: semantic routing with Apache Camel and Jev]
-*
https://camel.apache.org/blog/2026/09/camel-genai-observability-jbang/[Observe
your Camel AI routes with GenAI OpenTelemetry]
+* link:/blog/2026/09/securing-ai-agent-tools/[Authorizing what an AI agent may
do in Apache Camel]
+* link:/blog/2026/09/camel-spiffe-workload-identity/[Workload identity in
Apache Camel with SPIFFE and SPIRE]
+* link:/blog/2026/09/semantic-evaluation-system-one/[TypeSafe Jev meets Apache
Camel: semantic decisions in Camel routes]
+* link:/blog/2026/10/semantic-agent-routing/[One request, several agents:
semantic routing with Apache Camel and Jev]
+* link:/blog/2026/09/camel-genai-observability-jbang/[Observe your Camel AI
routes with GenAI OpenTelemetry]
See also xref:security-model.adoc[Security Model] for where Camel draws its
trust boundaries.
