feat: secret reference dependency tracking#5374
Conversation
✅ 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 enhances secret reference tracking by introducing a dependency tree visualization and revamping the UI. The backend now builds a recursive tree structure showing which secrets depend on a given secret, while the frontend uses the Key Changes:
Critical Issues:
Confidence Score: 2/5
Important Files Changed
|
Additional Comments (2)
Renaming the endpoint URL from Impact: Any external tools or scripts calling the old endpoint will break. Recommendation: Consider keeping the old endpoint as a deprecated alias that redirects to the new one, or clearly document this as a breaking change in release notes.
The response schema has been completely restructured from: { references: Array<...>, totalCount: number }to: { tree: SecretReferenceNodeTree }Impact: This is a breaking change that will break all existing API consumers expecting the old response format. Recommendation: Version this endpoint (e.g., |
Context
Added secret reference dependency tracking and revamped the secret reference tree UI.
Steps to verify the change
Type
Checklist
type(scope): short description(scope is optional, e.g.,fix: prevent crash on syncorfix(api): handle null response).