Conversation
Add OpenRouter as a new App Connection type to enable integration with OpenRouter's Provisioning API for managing API keys. Backend: - Add OpenRouter connection enums, schemas, types, and functions - Register OpenRouter connection router and validation - Add API docs for OpenRouter credentials Frontend: - Add OpenRouter to AppConnection enum and types - Create OpenRouterConnectionForm component - Add OpenRouter to APP_CONNECTION_MAP with logo - Register form in AppConnectionForm switch statements
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Greptile OverviewGreptile SummaryThis PR adds OpenRouter API key rotation support following the existing Secret Rotation V2 architecture. The implementation includes: App Connection (Phase 1):
Secret Rotation (Phase 2):
Key Changes:
Issues Found:
Confidence Score: 4/5
Important Files Changed
|
...d/src/ee/services/secret-rotation-v2/open-router-api-key/open-router-api-key-rotation-fns.ts
Show resolved
Hide resolved
backend/src/services/app-connection/open-router/open-router-connection-fns.ts
Show resolved
Hide resolved
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 22340054 | Triggered | Generic Password | cc18668 | frontend/src/pages/cert-manager/CertificateDetailsByIDPage/CertificateDetailsByIDPage.tsx | 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.
I think it is saying this because it thought part of the docs was talking about secrets? 🤔 |
...c/ee/services/secret-rotation-v2/open-router-api-key/open-router-api-key-rotation-schemas.ts
Outdated
Show resolved
Hide resolved
docs/documentation/platform/secret-rotation/open-router-api-key.mdx
Outdated
Show resolved
Hide resolved
...tend/src/components/secret-rotations-v2/forms/schemas/open-router-api-key-rotation-schema.ts
Outdated
Show resolved
Hide resolved
frontend/src/hooks/api/secretRotationsV2/types/open-router-api-key-rotation.ts
Show resolved
Hide resolved
this actually comes from router .. we could fix it by normalizing .. but I dont think its a good idea since they could fix it ? |



Context
This PR implements OpenRouter API Key secret rotation support for Infisical. It includes:
Phase 1 - App Connection:
Phase 2 - Secret Rotation:
The rotation follows the existing Secret Rotation V2 architecture:
issueCredentials: Creates initial API key via OpenRouter Provisioning APIrotateCredentials: Creates new key, updates secrets, then deletes the old inactive keyrevokeCredentials: Deletes all generated keys when rotation is removedRelated: SECRETS-71
Screenshots
Click to expand screenshots
Steps to verify the change
App Connection Tests
Secret Rotation Tests
OPEN_ROUTER_API_KEY)Edge Cases
Type
Checklist
type(scope): short description(scope is optional, e.g.,fix: prevent crash on syncorfix(api): handle null response).