Remove suggestion for converting from YAML to env vars for optimize c…

…onfig
camunda · Oct 30, 2024 · c8caa8c · c8caa8c
1 parent 0474ba6
commit c8caa8c
Show file tree

Hide file tree

Showing 6 changed files with 6 additions and 6 deletions.
diff --git a/optimize/self-managed/optimize-deployment/configuration/system-configuration.md b/optimize/self-managed/optimize-deployment/configuration/system-configuration.md
@@ -7,7 +7,7 @@ description: "An overview of all possible configuration options in Optimize."
 All distributions of Camunda Optimize come with a predefined set of configuration options that can be overwritten by the user, based on current environment requirements. To do that, have a look into the folder named `config` which contains a file called `environment-config.yaml` with values that override the default Optimize properties.
 
 :::note
-When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
+When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`).
 :::
 
 You can see a sample configuration file with all possible configuration fields

diff --git a/...n-3.10.0/self-managed/optimize-deployment/configuration/system-configuration.md b/...n-3.10.0/self-managed/optimize-deployment/configuration/system-configuration.md
@@ -7,7 +7,7 @@ description: "An overview of all possible configuration options in Optimize."
 All distributions of Camunda Optimize come with a predefined set of configuration options that can be overwritten by the user, based on current environment requirements. To do that, have a look into the folder named `config` which contains a file called `environment-config.yaml` with values that override the default Optimize properties.
 
 :::note
-When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
+When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`).
 :::
 
 You can see a sample configuration file with all possible configuration fields

diff --git a/...n-3.11.0/self-managed/optimize-deployment/configuration/system-configuration.md b/...n-3.11.0/self-managed/optimize-deployment/configuration/system-configuration.md
@@ -7,7 +7,7 @@ description: "An overview of all possible configuration options in Optimize."
 All distributions of Camunda Optimize come with a predefined set of configuration options that can be overwritten by the user, based on current environment requirements. To do that, have a look into the folder named `config` which contains a file called `environment-config.yaml` with values that override the default Optimize properties.
 
 :::note
-When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
+When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`).
 :::
 
 You can see a sample configuration file with all possible configuration fields

diff --git a/...n-3.12.0/self-managed/optimize-deployment/configuration/system-configuration.md b/...n-3.12.0/self-managed/optimize-deployment/configuration/system-configuration.md
@@ -7,7 +7,7 @@ description: "An overview of all possible configuration options in Optimize."
 All distributions of Camunda Optimize come with a predefined set of configuration options that can be overwritten by the user, based on current environment requirements. To do that, have a look into the folder named `config` which contains a file called `environment-config.yaml` with values that override the default Optimize properties.
 
 :::note
-When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
+When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`).
 :::
 
 You can see a sample configuration file with all possible configuration fields

diff --git a/...n-3.13.0/self-managed/optimize-deployment/configuration/system-configuration.md b/...n-3.13.0/self-managed/optimize-deployment/configuration/system-configuration.md
@@ -7,7 +7,7 @@ description: "An overview of all possible configuration options in Optimize."
 All distributions of Camunda Optimize come with a predefined set of configuration options that can be overwritten by the user, based on current environment requirements. To do that, have a look into the folder named `config` which contains a file called `environment-config.yaml` with values that override the default Optimize properties.
 
 :::note
-When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
+When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`).
 :::
 
 You can see a sample configuration file with all possible configuration fields

diff --git a/...n-3.14.0/self-managed/optimize-deployment/configuration/system-configuration.md b/...n-3.14.0/self-managed/optimize-deployment/configuration/system-configuration.md
@@ -7,7 +7,7 @@ description: "An overview of all possible configuration options in Optimize."
 All distributions of Camunda Optimize come with a predefined set of configuration options that can be overwritten by the user, based on current environment requirements. To do that, have a look into the folder named `config` which contains a file called `environment-config.yaml` with values that override the default Optimize properties.
 
 :::note
-When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
+When converting configuration properties to environment variables, ensure the `CAMUNDA_OPTIMIZE_` prefix is used (for example, `CAMUNDA_OPTIMIZE_API_ACCESSTOKEN`).
 :::
 
 You can see a sample configuration file with all possible configuration fields