clarify spring boot conventions for config, update spring links

docs/self-managed/console-deployment/configuration.md

@@ -9,7 +9,11 @@ description: "Read details on the configuration variables of Console Self-Manage
 Console Self-Managed is available only to [Enterprise customers](/reference/licenses.md#console).
 :::
 
-Console Self-Managed can be configured using environment variables and configuration parameters:
+Console Self-Managed can be configured using environment variables and configuration parameters.
+
+:::note
+Underscores in environment variables correspond to configuration file key levels.
+:::
 
 ## Environment variables
 

docs/self-managed/identity/deployment/configuration-variables.md

@@ -5,9 +5,8 @@ sidebar_label: "Configuration variables"
 description: "Learn more about core configuration, component configuration, database configuration, and feature flags."
 ---
 
-As Identity is a Spring Boot application, you may use the standard
-Spring [configuration](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config)
-methods.
+As a Spring Boot application, Identity supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
 ## Core configuration
 

docs/self-managed/operate-deployment/operate-configuration.md

@@ -3,15 +3,15 @@ id: operate-configuration
 title: Configuration
 ---
 
-Operate is a Spring Boot application. This means every way to [configure](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config)
-a Spring Boot application can be applied.
+As a Spring Boot application, Operate supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
 By default, the configuration for Operate is stored in a YAML file (`application.yml`). All Operate-related settings are prefixed with `camunda.operate`.
 
 :::note
-Configuration properties can also be defined as environment variables by converting to uppercase and replacing delimiters with `_`.
+Configuration properties can be defined as environment variables using [Spring Boot conventions](https://docs.spring.io/spring-boot/reference/features/external-config.html#features.external-config.typesafe-configuration-properties.relaxed-binding.environment-variables). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
 
-For example, the property `camunda.operate.elasticsearch.clustername` can be defined as the environment variable `CAMUNDA_OPERATE_ELASTICSEARCH_CLUSTERNAME`.
+For example, the property `camunda.operate.elasticsearch.clustername` is represented by the environment variable `CAMUNDA_OPERATE_ELASTICSEARCH_CLUSTERNAME`.
 :::
 
 The following parts are configurable:

docs/self-managed/tasklist-deployment/tasklist-configuration.md

@@ -3,9 +3,18 @@ id: tasklist-configuration
 title: Configuration
 ---
 
-Tasklist is a Spring Boot application. This means all provided ways to [configure](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config) a Spring Boot application can be applied.
+As a Spring Boot application, Tasklist supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
-By default, the configuration for Tasklist is stored in a YAML file `application.yml`. All Tasklist-related settings are prefixed with `camunda.tasklist`. The following components are configurable:
+By default, the configuration for Tasklist is stored in a YAML file `application.yml`. All Tasklist-related settings are prefixed with `camunda.tasklist`.
+
+:::note
+Configuration properties can be defined as environment variables using [Spring Boot conventions](https://docs.spring.io/spring-boot/reference/features/external-config.html#features.external-config.typesafe-configuration-properties.relaxed-binding.environment-variables). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
+
+For example, the property `server.servlet.context-path` is represented by the environment variable `SERVER_SERVLET_CONTEXT_PATH`.
+:::
+
+The following components are configurable:
 
 ## Webserver
 

docs/self-managed/zeebe-deployment/configuration/configuration.md

@@ -85,7 +85,7 @@ Rename the configuration file to `application.yaml` and place it in the followin
 
 ### Other ways to specify the configuration file
 
-Zeebe uses Spring Boot for its configuration parsing. All other ways to [configure a Spring Boot application](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config) should also work. In particular, you can use:
+Zeebe uses Spring Boot for its configuration parsing. All other ways to [configure a Spring Boot application](https://docs.spring.io/spring-boot/reference/features/external-config.html) should also work. In particular, you can use:
 
 - `SPRING_CONFIG_ADDITIONAL_LOCATION` to specify an additional configuration file.
 - `SPRING_APPLICATION_JSON` to specify settings in JSON format.

docs/self-managed/zeebe-deployment/configuration/environment-variables.md

@@ -6,7 +6,8 @@ description: "Let's take a closer look at the environment variables for configur
 
 ## Environment variables for configuration
 
-The configuration can be provided as a file or through environment variables. Mixing both sources is also possible. In that case, environment variables have precedence over the configuration settings in the configuration file.
+As a Spring Boot application, Zeebe supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method. This configuration can be provided as a configuration file, through environment variables, or both. When both sources are used, environment variables have precedence over the configuration file.
 
 All available environment variables are documented in the [configuration file templates](configuration.md#configuration-file-templates).
 

versioned_docs/version-1.3/self-managed/zeebe-deployment/configuration/configuration.md

@@ -85,7 +85,7 @@ Rename the configuration file to `application.yaml` and place it in the followin
 
 ### Other ways to specify the configuration file
 
-Zeebe uses Spring Boot for its configuration parsing. All other ways to [configure a Spring Boot application](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config) should also work. In particular, you can use:
+Zeebe uses Spring Boot for its configuration parsing. All other ways to [configure a Spring Boot application](https://docs.spring.io/spring-boot/reference/features/external-config.html) should also work. In particular, you can use:
 
 - `SPRING_CONFIG_ADDITIONAL_LOCATION` to specify an additional configuration file.
 - `SPRING_APPLICATION_JSON` to specify settings in JSON format.

versioned_docs/version-1.3/self-managed/zeebe-deployment/configuration/environment-variables.md

@@ -6,7 +6,8 @@ description: "Let's take a closer look at the environment variables for configur
 
 ## Environment variables for configuration
 
-The configuration can be provided as a file or through environment variables. Mixing both sources is also possible. In that case, environment variables have precedence over the configuration settings in the configuration file.
+As a Spring Boot application, Zeebe supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method. This configuration can be provided as a configuration file, through environment variables, or both. When both sources are used, environment variables have precedence over the configuration file.
 
 All available environment variables are documented in the [configuration file templates](configuration.md#configuration-file-templates).
 

versioned_docs/version-8.2/self-managed/identity/deployment/configuration-variables.md

@@ -5,9 +5,8 @@ sidebar_label: "Configuration variables"
 description: "Learn more about core configuration, component configuration, database configuration, and feature flags."
 ---
 
-As Identity is a Spring Boot application, you may use the standard
-Spring [configuration](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config)
-methods.
+As a Spring Boot application, Identity supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
 ### Core configuration
 

versioned_docs/version-8.2/self-managed/operate-deployment/operate-configuration.md

@@ -3,15 +3,15 @@ id: operate-configuration
 title: Configuration
 ---
 
-Operate is a Spring Boot application. This means every way to [configure](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config)
-a Spring Boot application can be applied.
+As a Spring Boot application, Operate supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
 By default, the configuration for Operate is stored in a YAML file (`application.yml`). All Operate-related settings are prefixed with `camunda.operate`.
 
 :::note
-Configuration properties can also be defined as environment variables by converting to uppercase and replacing delimiters with `_`.
+Configuration properties can be defined as environment variables using [Spring Boot conventions](https://docs.spring.io/spring-boot/reference/features/external-config.html#features.external-config.typesafe-configuration-properties.relaxed-binding.environment-variables). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
 
-For example, the property `camunda.operate.elasticsearch.clustername` can be defined as the environment variable `CAMUNDA_OPERATE_ELASTICSEARCH_CLUSTERNAME`.
+For example, the property `camunda.operate.elasticsearch.clustername` is represented by the environment variable `CAMUNDA_OPERATE_ELASTICSEARCH_CLUSTERNAME`.
 :::
 
 The following parts are configurable:

versioned_docs/version-8.2/self-managed/tasklist-deployment/tasklist-configuration.md

@@ -3,9 +3,18 @@ id: tasklist-configuration
 title: Configuration
 ---
 
-Tasklist is a Spring Boot application. This means all provided ways to [configure](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config) a Spring Boot application can be applied.
+As a Spring Boot application, Tasklist supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
-By default, the configuration for Tasklist is stored in a YAML file `application.yml`. All Tasklist-related settings are prefixed with `camunda.tasklist`. The following components are configurable:
+By default, the configuration for Tasklist is stored in a YAML file `application.yml`. All Tasklist-related settings are prefixed with `camunda.tasklist`.
+
+:::note
+Configuration properties can be defined as environment variables using [Spring Boot conventions](https://docs.spring.io/spring-boot/reference/features/external-config.html#features.external-config.typesafe-configuration-properties.relaxed-binding.environment-variables). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
+
+For example, the property `server.servlet.context-path` is represented by the environment variable `SERVER_SERVLET_CONTEXT_PATH`.
+:::
+
+The following components are configurable:
 
 - [Webserver](#webserver)
 - [Elasticsearch](#elasticsearch)

versioned_docs/version-8.2/self-managed/zeebe-deployment/configuration/configuration.md

@@ -87,7 +87,7 @@ Rename the configuration file to `application.yaml` and place it in the followin
 
 ### Other ways to specify the configuration file
 
-Zeebe uses Spring Boot for its configuration parsing. All other ways to [configure a Spring Boot application](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config) should also work. In particular, you can use:
+Zeebe uses Spring Boot for its configuration parsing. All other ways to [configure a Spring Boot application](https://docs.spring.io/spring-boot/reference/features/external-config.html) should also work. In particular, you can use:
 
 - `SPRING_CONFIG_ADDITIONAL_LOCATION` to specify an additional configuration file.
 - `SPRING_APPLICATION_JSON` to specify settings in JSON format.

versioned_docs/version-8.2/self-managed/zeebe-deployment/configuration/environment-variables.md

@@ -6,7 +6,8 @@ description: "Let's take a closer look at the environment variables for configur
 
 ## Environment variables for configuration
 
-The configuration can be provided as a file or through environment variables. Mixing both sources is also possible. In that case, environment variables have precedence over the configuration settings in the configuration file.
+As a Spring Boot application, Zeebe supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method. This configuration can be provided as a configuration file, through environment variables, or both. When both sources are used, environment variables have precedence over the configuration file.
 
 All available environment variables are documented in the [configuration file templates](configuration.md#configuration-file-templates).
 

versioned_docs/version-8.3/self-managed/identity/deployment/configuration-variables.md

@@ -5,9 +5,8 @@ sidebar_label: "Configuration variables"
 description: "Learn more about core configuration, component configuration, database configuration, and feature flags."
 ---
 
-As Identity is a Spring Boot application, you may use the standard
-Spring [configuration](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config)
-methods.
+As a Spring Boot application, Identity supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
 ## Core configuration
 

versioned_docs/version-8.3/self-managed/operate-deployment/operate-configuration.md

@@ -3,15 +3,15 @@ id: operate-configuration
 title: Configuration
 ---
 
-Operate is a Spring Boot application. This means every way to [configure](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config)
-a Spring Boot application can be applied.
+As a Spring Boot application, Operate supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
 By default, the configuration for Operate is stored in a YAML file (`application.yml`). All Operate-related settings are prefixed with `camunda.operate`.
 
 :::note
-Configuration properties can also be defined as environment variables by converting to uppercase and replacing delimiters with `_`.
+Configuration properties can be defined as environment variables using [Spring Boot conventions](https://docs.spring.io/spring-boot/reference/features/external-config.html#features.external-config.typesafe-configuration-properties.relaxed-binding.environment-variables). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
 
-For example, the property `camunda.operate.elasticsearch.clustername` can be defined as the environment variable `CAMUNDA_OPERATE_ELASTICSEARCH_CLUSTERNAME`.
+For example, the property `camunda.operate.elasticsearch.clustername` is represented by the environment variable `CAMUNDA_OPERATE_ELASTICSEARCH_CLUSTERNAME`.
 :::
 
 The following parts are configurable:

versioned_docs/version-8.3/self-managed/tasklist-deployment/tasklist-configuration.md

@@ -3,9 +3,18 @@ id: tasklist-configuration
 title: Configuration
 ---
 
-Tasklist is a Spring Boot application. This means all provided ways to [configure](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config) a Spring Boot application can be applied.
+As a Spring Boot application, Tasklist supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
-By default, the configuration for Tasklist is stored in a YAML file `application.yml`. All Tasklist-related settings are prefixed with `camunda.tasklist`. The following components are configurable:
+By default, the configuration for Tasklist is stored in a YAML file `application.yml`. All Tasklist-related settings are prefixed with `camunda.tasklist`.
+
+:::note
+Configuration properties can be defined as environment variables using [Spring Boot conventions](https://docs.spring.io/spring-boot/reference/features/external-config.html#features.external-config.typesafe-configuration-properties.relaxed-binding.environment-variables). To define an environment variable, convert the configuration property to uppercase, remove any dashes, and replace any delimiters (`.`) with `_`.
+
+For example, the property `server.servlet.context-path` is represented by the environment variable `SERVER_SERVLET_CONTEXT_PATH`.
+:::
+
+The following components are configurable:
 
 ## Webserver
 

versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/configuration.md

@@ -87,7 +87,7 @@ Rename the configuration file to `application.yaml` and place it in the followin
 
 ### Other ways to specify the configuration file
 
-Zeebe uses Spring Boot for its configuration parsing. All other ways to [configure a Spring Boot application](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config) should also work. In particular, you can use:
+Zeebe uses Spring Boot for its configuration parsing. All other ways to [configure a Spring Boot application](https://docs.spring.io/spring-boot/reference/features/external-config.html) should also work. In particular, you can use:
 
 - `SPRING_CONFIG_ADDITIONAL_LOCATION` to specify an additional configuration file.
 - `SPRING_APPLICATION_JSON` to specify settings in JSON format.

versioned_docs/version-8.3/self-managed/zeebe-deployment/configuration/environment-variables.md

@@ -6,7 +6,8 @@ description: "Let's take a closer look at the environment variables for configur
 
 ## Environment variables for configuration
 
-The configuration can be provided as a file or through environment variables. Mixing both sources is also possible. In that case, environment variables have precedence over the configuration settings in the configuration file.
+As a Spring Boot application, Zeebe supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method. This configuration can be provided as a configuration file, through environment variables, or both. When both sources are used, environment variables have precedence over the configuration file.
 
 All available environment variables are documented in the [configuration file templates](configuration.md#configuration-file-templates).
 

versioned_docs/version-8.4/self-managed/console-deployment/configuration.md

@@ -9,7 +9,11 @@ description: "Read details on the configuration variables of Console Self-Manage
 Console Self-Managed is available only to [Enterprise customers](../../reference/licenses.md#console).
 :::
 
-Console Self-Managed can be configured using environment variables and configuration parameters:
+Console Self-Managed can be configured using environment variables and configuration parameters.
+
+:::note
+Underscores in environment variables correspond to configuration file key levels.
+:::
 
 ## Environment variables
 

versioned_docs/version-8.4/self-managed/identity/deployment/configuration-variables.md

@@ -5,9 +5,8 @@ sidebar_label: "Configuration variables"
 description: "Learn more about core configuration, component configuration, database configuration, and feature flags."
 ---
 
-As Identity is a Spring Boot application, you may use the standard
-Spring [configuration](https://docs.spring.io/spring-boot/docs/current/reference/html/spring-boot-features.html#boot-features-external-config)
-methods.
+As a Spring Boot application, Identity supports any standard
+[Spring configuration](https://docs.spring.io/spring-boot/reference/features/external-config.html) method.
 
 ### Core configuration