SCALE-122: Document Bitbucket property translation (#970)

Author: mmuthusamy-atlassian

docs/docs/containers/BITBUCKET-MESH.md

@@ -103,6 +103,12 @@ can also be provided via Docker environment variables. For a full explanation of
 variables see
 [the relevant Spring Boot documentation](https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html#boot-features-external-config-relaxed-binding).
 
+To translate a property name into an environment variable:
+
+* dot `.` becomes underscore `_`
+* dash `-` becomes underscore `_`
+* Example: `this.new-property` becomes `THIS_NEW_PROPERTY`
+
 ## Container Configuration
 
 * `SET_PERMISSIONS` (default: true)

docs/docs/containers/BITBUCKET.md

@@ -194,6 +194,12 @@ can also be provided via Docker environment variables. For a full explanation of
 variables see
 [the relevant Spring Boot documentation](https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html#boot-features-external-config-relaxed-binding).
 
+To translate a property name into an environment variable:
+
+* dot `.` becomes underscore `_`
+* dash `-` becomes underscore `_`
+* Example: `this.new-property` becomes `THIS_NEW_PROPERTY`
+
 For example, a full command-line for a Bitbucket node with a PostgreSQL
 database, and an external OpenSearch instance might look like:
 

docs/docs/userguide/CONFIGURATION.md

@@ -326,9 +326,9 @@ this behaviour may be undesirable; this flag forces an update of all
 generated files.
 
 The affected files are:
-* Jira: `dbconfig.xml`
-* Confluence: `confluence.cfg.xml`
-* Bamboo: `bamboo.cfg.xml`
+- Jira: `dbconfig.xml`
+- Confluence: `confluence.cfg.xml`
+- Bamboo: `bamboo.cfg.xml`
 
 To force update of the configuration files when pods restart, set `<product_name.forceConfigUpdate>` to true.
 You can do it by passing an argument to helm install/update command:
@@ -342,6 +342,36 @@ jira:
   forceConfigUpdate: true
 ```
 
+!!!info "Bitbucket and Bitbucket Mesh configuration file"
+    It's not possible to generate the Bitbucket and Bitbucket Mesh configuration files.
+    Bitbucket uses `${BITBUCKET_HOME}/shared/bitbucket.properties`. The properties are from 
+    [bitbucket.properties file](https://confluence.atlassian.com/bitbucketserver/bitbucket-server-config-properties-776640155.html) 
+    and can be provided as environment variables. For example:
+    ```yaml
+    bitbucket:
+      additionalEnvironmentVariables:
+      - name: SEACRH_ENABLED
+        value: false
+      - name: PLUGIN_SEARCH_CONFIG_BASEURL
+        value: http://my.opensearch.host
+    ```
+    Bitbucket Mesh uses `${BITBUCKET_HOME}/mesh.properties`. The properties are from 
+    [mesh.properties file](https://confluence.atlassian.com/bitbucketserver/mesh-configuration-properties-1128304362.html) 
+    and can be provided as environment variables. For example:
+    ```yaml
+    bitbucket:
+      mesh:
+        additionalEnvironmentVariables:
+        - name: GIT_PATH_EXECUTABLE
+          value: /usr/bin/git
+    ```
+
+    To translate property into an environment variable:
+
+    * dot `.` becomes underscore `_`
+    * dash `-` becomes underscore `_`
+    * Example: `this.new-property` becomes `THIS_NEW_PROPERTY`
+
 ## :material-book-cog: Additional libraries & plugins
 
 The products' Docker images contain the default set of bundled libraries and plugins.