Add MySQL Replication Mode Transform Ops-Request

[AshrafulHaqueToni]

Signed-off-by: Ashraful Haque Tani [email protected]

[github-actions[bot]]

Visit the preview URL for this PR (updated for commit 106270f):

https://kubedb-v2-hugo--pr733-my-upd-saai4pt8.web.app

_{(expires Mon, 07 Jul 2025 09:48:28 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 0f29ae8ae0bd54a99bf2b223b6833be47acd5943}

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
591529	Triggered	Generic Password	795a72cacf3b8327fb20b78458296c6480f32483	docs/guides/mysql/replication-mode-transform/replication-mode-transform/examples/mysql-singapore-auth.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[ArnobKumarSaha]

Ready for merge ?

[Neaj-Morshad-101]

Ready for merge ?

NO