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 gateway credential handling to enable credential reusability across multiple vault operations. The main change encapsulates V1 gateway relay details (host, port, TLS options, identity) into a single Key improvements:
The refactoring maintains backward compatibility - when Confidence Score: 4/5
Important Files Changed
Last reviewed commit: 190022a |
|
@greptile re-review the PR and update your summary |
scott-ray-wilson
left a comment
There was a problem hiding this comment.
LGTM, we verified together walking through in call
Context
Added reusable gateway for vault-specific requests. You can now pass pre-created gateway credentials when doing vault requests, and it will use those instead of getting new ones. This was done to resolve an issue with the in-platform vault migration tooling failing when the vault instance has a large number of policies. It would fail to even configure the vault migration tooling because our postgres pool would be exhausted because we use advisory locks when obtaining the relay credentials.
Note: I've had to update the types across parts of the backend that uses the v1 gatway to make typescript play ball.
Type
Checklist
type(scope): short description(scope is optional, e.g.,fix: prevent crash on syncorfix(api): handle null response).