Remove suggestion to convert from YAML to env vars for optimize config

optimize/self-managed/optimize-deployment/configuration/system-configuration.md

@@ -6,10 +6,6 @@ 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 `_`.
-:::
-
 You can see a sample configuration file with all possible configuration fields
 and their default values [here](service-config.yaml).
 

optimize_versioned_docs/version-3.10.0/self-managed/optimize-deployment/configuration/system-configuration.md

@@ -6,10 +6,6 @@ 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 `_`.
-:::
-
 You can see a sample configuration file with all possible configuration fields
 and their default values [here](service-config.yaml).
 

optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/configuration/system-configuration.md

@@ -6,10 +6,6 @@ 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 `_`.
-:::
-
 You can see a sample configuration file with all possible configuration fields
 and their default values [here](service-config.yaml).
 

optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/configuration/system-configuration.md

@@ -6,10 +6,6 @@ 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 `_`.
-:::
-
 You can see a sample configuration file with all possible configuration fields
 and their default values [here](service-config.yaml).
 

optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/configuration/system-configuration.md

@@ -6,10 +6,6 @@ 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 `_`.
-:::
-
 You can see a sample configuration file with all possible configuration fields
 and their default values [here](service-config.yaml).
 

optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/configuration/system-configuration.md

@@ -6,10 +6,6 @@ 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 `_`.
-:::
-
 You can see a sample configuration file with all possible configuration fields
 and their default values [here](service-config.yaml).