添加代码生成接口

[little3201]

添加代码生成接口

[sonarqubecloud]

Quality Gate failed

Failed conditions
15.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[gitguardian]

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

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9320164	Triggered	Username Password	56a66ab	exploiter/target/classes/application-prod.yaml	View secret
9320164	Triggered	Username Password	56a66ab	hypervisor/src/main/resources/application-prod.yaml	View secret
9320164	Triggered	Username Password	56a66ab	assets/src/main/resources/application-dev.yaml	View secret
9320164	Triggered	Username Password	56a66ab	exploiter/src/main/resources/application-prod.yaml	View secret
9320164	Triggered	Username Password	56a66ab	exploiter/target/classes/application-dev.yaml	View secret
9320164	Triggered	Username Password	56a66ab	assets/src/main/resources/application-prod.yaml	View secret
9320164	Triggered	Username Password	56a66ab	auth/src/main/resources/application-prod.yml	View secret
9320164	Triggered	Username Password	56a66ab	auth/src/main/resources/application-dev.yml	View secret
9320164	Triggered	Username Password	56a66ab	exploiter/src/main/resources/application-dev.yaml	View secret
9320164	Triggered	Username Password	56a66ab	hypervisor/src/main/resources/application-dev.yaml	View secret
9320164	Triggered	Username Password	4094531	exploiter/target/classes/application-prod.yaml	View secret
9320164	Triggered	Username Password	4094531	exploiter/target/classes/application-dev.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 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.}