From 991344ddfa645c7a44e396b981f04add58b2694b Mon Sep 17 00:00:00 2001
From: Akash Jain <15995028+akash-jain-10@users.noreply.github.com>
Date: Fri, 9 Sep 2022 02:43:41 +0530
Subject: [PATCH] Add Database Connection Environment Variables docs (#7350)

---
 .../content/deployment/upgrade/versions/011-to-012.md     | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/openmetadata-docs/content/deployment/upgrade/versions/011-to-012.md b/openmetadata-docs/content/deployment/upgrade/versions/011-to-012.md
index 341d81f33fc..a3c8c313a4c 100644
--- a/openmetadata-docs/content/deployment/upgrade/versions/011-to-012.md
+++ b/openmetadata-docs/content/deployment/upgrade/versions/011-to-012.md
@@ -5,11 +5,15 @@ slug: /deployment/upgrade/versions/011-to-012
 
 # Upgrade from 0.11 to 0.12
 
-Upgrading from 0.11 to 0.12 can be done directly on your instances. This page will list a couple of details that you
-should take into consideration when running the upgrade.
+Upgrading from 0.11 to 0.12 can be done directly on your instances. This page will list a couple of details that you should take into consideration when running the upgrade.
 
 ## Highlights
 
+### Database Connection Environment Variables
+
+On 0.11, the Environment Variables to connect to Database used were MYSQL_USER, MYSQL_USER_PASSWORD, MYSQL_HOST, MYSQL_PORT, MYSQL_DATABASE. These environment variables are changed in 0.12 Release with DB_USER, DB_USER_PASSWORD, DB_HOST, DB_PORT, OM_DATABASE. This will effect to all the bare metal and docker instances which configures a custom database depending on the above environment variable values.
+This change is however not affected for Kubernetes deployments.
+
 ### Data Profiler and Data Quality Tests
 
 On 0.11, the Profiler Workflow handled two things: