From bc432bb3c7b47b332656276ee886b6f79a9c65e4 Mon Sep 17 00:00:00 2001
From: Sebastian Widmer <widmer.sebastian@gmail.com>
Date: Thu, 18 Dec 2025 09:14:58 +0100
Subject: [PATCH] Clarify usage of printf over echo for displaying env
 variables

---
 docs/modules/ROOT/pages/how-to/use-custom-grafana.adoc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/modules/ROOT/pages/how-to/use-custom-grafana.adoc b/docs/modules/ROOT/pages/how-to/use-custom-grafana.adoc
index 2365c7f..000bb7f 100644
--- a/docs/modules/ROOT/pages/how-to/use-custom-grafana.adoc
+++ b/docs/modules/ROOT/pages/how-to/use-custom-grafana.adoc
@@ -154,7 +154,9 @@ We recommend to fall back to `GET`.
 [NOTE]
 ====
 You need to substitute `$CA`, `$TOKEN`, and `$\{APP_NAMESPACE}` with the values of the environment variables set earlier.
-You can easily display their contents using `echo`.
+You can easily display their contents using `printf "%s" "$CA"`.
+
+Note that using `echo` to output variables might mangle line breaks and could lead to the configuration failing.
 
 Make sure to not use quotes for the custom query parameters.
 Using `namespace="my-app"` will result in permission errors, use `namespace=my-app`.