Skip to content

Conversation

@biswasurmi
Copy link
Member

No description provided.

urmi added 30 commits November 19, 2025 17:55
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
Signed-off-by: urmi <[email protected]>
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Neaj-Morshad-101
❌ urmi


urmi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@gitguardian
Copy link

gitguardian bot commented Dec 4, 2025

⚠️ 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
21707712 Triggered Generic Password d2c4be7 apis/kubedb/constants.go 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


🦉 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.

@Neaj-Morshad-101 Neaj-Morshad-101 marked this pull request as draft December 4, 2025 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants