🔄 Preview: [TT-16268] New secrets management capability - #2783
Draft
probelabs[bot] wants to merge 475 commits into
Draft
🔄 Preview: [TT-16268] New secrets management capability#2783probelabs[bot] wants to merge 475 commits into
probelabs[bot] wants to merge 475 commits into
probelabs / Visor: performance
succeeded
Aug 24, 2026 in 40s
✅ Check Passed (Warnings Found)
performance check passed. Found 1 warning, but fail_if condition was not met.
Details
📊 Summary
- Total Issues: 1
- Warning Issues: 1
🔍 Failure Condition Results
Passed Conditions
- global_fail_if: Condition passed
Issues by Category
Performance (1)
⚠️ tyk-configuration-reference/kv-store-legacy.mdx:52 - The documentation describes a legacy feature ($secret_*notation in transformation middleware) that resolves secrets on every request. This operation introduces significant overhead and latency to each API call, especially with remote secret stores like Vault or Consul. While the documentation now includes a warning about this, the feature itself remains a potential performance bottleneck for systems that rely on it.
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check warning on line 56 in tyk-configuration-reference/kv-store-legacy.mdx
probelabs / Visor: performance
performance Issue
The documentation describes a legacy feature (`$secret_*` notation in transformation middleware) that resolves secrets on every request. This operation introduces significant overhead and latency to each API call, especially with remote secret stores like Vault or Consul. While the documentation now includes a warning about this, the feature itself remains a potential performance bottleneck for systems that rely on it.
Raw output
The added warning is a good mitigation from a documentation perspective. Users requiring dynamic, per-request secret resolution should be aware of the performance impact. If possible, they should consider alternative patterns, such as caching secret values with a short TTL or using a secret store with very low latency. The new `kv://` notation, which resolves secrets at load time, should be preferred for all use cases that do not strictly require per-request values.
Loading