TRV11 TSP Buyer Logs

[Nirdosh3312]

Submitting logs for Buyer Application for Metro (ONDC:TRV11)

[gitguardian]

⚠️ GitGuardian has uncovered 6 secrets 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
7620759	Triggered	Generic High Entropy Secret	a897d4e	TRV11/Sequelstring/Flow 1/on_confirm.json	View secret
7620759	Triggered	Generic High Entropy Secret	a897d4e	TRV11/Sequelstring/Flow 2/on_confirm.json	View secret
7620759	Triggered	Generic High Entropy Secret	a897d4e	TRV11/Sequelstring/Flow 2/on_cancel(soft).json	View secret
7620759	Triggered	Generic High Entropy Secret	a897d4e	TRV11/Sequelstring/Flow 2/on_confirm.json	View secret
7620759	Triggered	Generic High Entropy Secret	a897d4e	TRV11/Sequelstring/Flow 1/on_confirm.json	View secret
7620759	Triggered	Generic High Entropy Secret	a897d4e	TRV11/Sequelstring/Flow 2/on_cancel(soft).json	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}

[sourabhsaini11]

@Nirdosh3312, instead of updating old logs(2.0.0) to newer version(2.0.1), please move them inside a separate folder so that logs for all versions can be present.

[Nirdosh3312]

Hi @sourabhsaini11 They are for the same version, we are submitting them again for the verification of TSP Buyer Application

[sourabhsaini11]

@Nirdosh3312, Your current logs for METRO will update the past approved logs submitted by your team for Intra-city.Please get the folder structure fixed