Updates/srql integration x2 #2217

Merged

mfreeman451 merged 3 commits from refs/pull/2217/head into main

2025-09-13 00:23:56 +00:00

mfreeman451 commented

2025-09-13 00:15:44 +00:00

(Migrated from github.com)

Owner

Imported from GitHub pull request.

Original GitHub pull request: #1634
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/1634
Original created: 2025-09-13T00:15:44Z
Original updated: 2025-09-13T00:24:12Z
Original head: carverauto/serviceradar:updates/srql_integration_x2
Original base: main
Original merged: 2025-09-13T00:23:56Z by @mfreeman451

No description provided.

Imported from GitHub pull request. Original GitHub pull request: #1634 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/pull/1634 Original created: 2025-09-13T00:15:44Z Original updated: 2025-09-13T00:24:12Z Original head: carverauto/serviceradar:updates/srql_integration_x2 Original base: main Original merged: 2025-09-13T00:23:56Z by @mfreeman451 --- _No description provided._

gitguardian[bot] commented

2025-09-13 00:15:49 +00:00

(Migrated from github.com)

Author

Owner

Imported GitHub PR comment.

Original author: @gitguardian[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/1634#issuecomment-3287226005
Original created: 2025-09-13T00:15:49Z

⚠️ 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
20790156	Triggered	Generic Password	`9320bdc0e8`	ocaml/srql/test/test_simple_connection.ml	View secret

🛠 Guidelines to remediate hardcoded secrets

Understand the implications of revoking this secret by investigating where it is used in your code.
Replace and store your secret safely. Learn here the best practices.
Revoke and rotate this secret.
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.}

Imported GitHub PR comment. Original author: @gitguardian[bot] Original URL: https://github.com/carverauto/serviceradar/pull/1634#issuecomment-3287226005 Original created: 2025-09-13T00:15:49Z --- #### ⚠️ 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. <details> <summary>🔎 Detected hardcoded secret in your pull request</summary> | GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [20790156](https://dashboard.gitguardian.com/workspace/312055/incidents/20790156?occurrence=212734404) | Triggered | Generic Password | 9320bdc0e8729fd697c402ecbf213ce4aac995dd | ocaml/srql/test/test_simple_connection.ml | [View secret](https://github.com/carverauto/serviceradar/commit/9320bdc0e8729fd697c402ecbf213ce4aac995dd#diff-414b2c95a515bbae22db029e3b9f87c4931aaef886a2b8b4a9f13e9cc0c521eeR13) | </details> <details> <summary>🛠 Guidelines to remediate hardcoded secrets</summary> 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](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_password#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 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](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation. </details> --- 🦉 [GitGuardian](https://dashboard.gitguardian.com/auth/login/?utm_medium=checkruns&utm_source=github&utm_campaign=cr1) 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.