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 2927376faa9 Fix website build
2927376faa9 is described below
commit 2927376faa92b01ab7a9af05c91285b42a681fbf
Author: Claus Ibsen <[email protected]>
AuthorDate: Mon Oct 14 17:12:29 2024 +0200
Fix website build
---
docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
index 11c09626a73..c3b4ec227f8 100644
--- a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
+++ b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
@@ -279,7 +279,7 @@ type: Opaque
You can mount it in your Pod container, for instance, under
`/etc/camel/conf.d/_secrets/my-secret`. Now, just make your Camel application
be aware where to scan your configuration via
`camel.main.cloud-properties-location = /etc/camel/conf.d/_secrets/my-secret`
application properties. It's a comma separated value, so, you can add as many
Secrets/Configmaps you need.
-At runtime, you will be able to read the configuration transparently as `\{{
my-property \}}` as you're doing with the rest of properties.
+At runtime, you will be able to read the configuration transparently as ```{{
my-property }}``` as you're doing with the rest of properties.
NOTE: the same configuration works with Configmap.
