From 6a4db1742b1c9e2b4566c126ca634155d7e2f1c9 Mon Sep 17 00:00:00 2001 From: Andres Martinez Gotor Date: Thu, 12 Dec 2024 15:05:47 +0100 Subject: [PATCH] Docs: Clarify environment variable usage in provisioning (#97848) --- docs/sources/administration/provisioning/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/administration/provisioning/index.md b/docs/sources/administration/provisioning/index.md index 34f32dbbc4f..5c164a708aa 100644 --- a/docs/sources/administration/provisioning/index.md +++ b/docs/sources/administration/provisioning/index.md @@ -39,7 +39,7 @@ packages, then your configuration file is located at You can use environment variable interpolation in all three provisioning configuration types. The allowed syntax is either `$ENV_VAR_NAME` or `${ENV_VAR_NAME}`, and it can be used only for values, not for keys or larger parts -of the configurations. +of the configurations. If the environment variable value has a `$` (e.g. `Pa$sw0rd`), use the `$ENV_VAR_NAME` syntax to avoid double expansion. It's not available in the dashboard's definition files, just the dashboard provisioning configuration.