Conversation
This prevents cache invalidation on every deployment. Previously, the entire secrets cache would become invalid when deploying a new Infisical version since INFISICAL_PLATFORM_VERSION was included in the cache key computation. This caused expensive 'with recursive' computations for all secret requests against new containers. Co-Authored-By: maidul@infisical.com <maidul98@gmail.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
✅ 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 removes Changes:
Impact: Confidence Score: 5/5
Important Files Changed
|
Context
Every time a new Infisical version is deployed, the entire secrets cache becomes invalid because
INFISICAL_PLATFORM_VERSIONwas included in the cache key computation. This caused all secret requests against new containers to perform expensiveWITH RECURSIVEdatabase queries since there was no "existing" cache for the new version.This PR removes the platform version from the cache key, so deployments no longer invalidate the secrets cache.
Before: Cache key was
secret-manager:{version}:{projectId}:...After: Cache key is
secret-manager:{projectId}:...Related Slack discussion concluded that secret structure changes are rare enough (2-3 times/year) that the tradeoff is acceptable.
Steps to verify the change
SecretServiceCacheKeys.productKeyno longer includes the platform versiongetConfigimport was removedType
Checklist
Requested by: @maidul98
Link to Devin run: https://app.devin.ai/sessions/3e861d270d834407a0bbd54c1345d6cb