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 refactors the V4 secrets router to provide explicit control over personal secret overrides through a new Key Changes:
Backward Compatibility: Confidence Score: 4/5
Important Files Changed
|
Additional Comments (1)
This file already uses Also consider RE2 equivalents for other string/regex operations in this file if they are regex-driven. |
|
@greptile i've made some larger changes since your last review. review this PR thoroughly. some notes: |
Additional Comments (1)
|
|
@greptile update your summary with my comments to your previous comments in mind |
Context
Larger changes to the V4 secrets router. The user now explictly has to request for personal secrets to be included in the request. The user needs to pass
includePersonalOverrides=truewhen doing the request for personal secrets to be fetched. Additionally, this now functions with a priority mechanism which means duplicate shared / personal secrets will no longer be returned. If there is a personal secret, the personal secret will take priority and the shared secret will be stripped out of the response. Personal secrets now also support referencing other personal secrets.Other changes to the v4 rotuer:
include_importsrenamed toincludeImports, and now defaults to true.What this means for the v3 router
The V3 router will continue to work as before by including both personal and shared secrets in the response, with no way to configure the behavior.
Type
Checklist
type(scope): short description(scope is optional, e.g.,fix: prevent crash on syncorfix(api): handle null response).