From 1cbcdd01d2d50352b238d744bd04046790deaa93 Mon Sep 17 00:00:00 2001
From: Akash Jain <15995028+akash-jain-10@users.noreply.github.com>
Date: Sat, 4 Nov 2023 22:26:13 +0530
Subject: [PATCH] docs: Add breaking changes for the use of `DB_PARAMS`
 (#13841)

---
 .../v1.2/deployment/upgrade/upgrade-prerequisites.md        | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/openmetadata-docs/content/partials/v1.2/deployment/upgrade/upgrade-prerequisites.md b/openmetadata-docs/content/partials/v1.2/deployment/upgrade/upgrade-prerequisites.md
index a913b68113f..eb88dac46bb 100644
--- a/openmetadata-docs/content/partials/v1.2/deployment/upgrade/upgrade-prerequisites.md
+++ b/openmetadata-docs/content/partials/v1.2/deployment/upgrade/upgrade-prerequisites.md
@@ -109,6 +109,12 @@ After the migration is finished, you can revert this changes.
 
 # Breaking Changes
 
+### Database connection SSL Configuration
+
+With 1.2.X, the environment variable `DB_USE_SSL` is deprecated in favour of `DB_PARAMS`.
+For Bare Metal and Docker Deployment, Add / Update the variable `DB_PARAMS` to `allowPublicKeyRetrieval=true&useSSL=true&serverTimezone=UTC` to enable ssl security to connect to database.
+For Kubernetes Deployment, `openmetadata.config.database.dbParams` is available to pass the above values as helm values.
+
 ### Version Upgrades
 
 - The OpenMetadata Server is now based on **JDK 17**