[TT-17611] IAM authentication for Google Cloud - #2766
Merged
probelabs / Visor: performance
succeeded
Aug 26, 2026 in 47s
✅ Check Passed (Warnings Found)
performance check passed. Found 2 warnings, but fail_if condition was not met.
Details
📊 Summary
- Total Issues: 2
- Warning Issues: 2
🔍 Failure Condition Results
Passed Conditions
- global_fail_if: Condition passed
Issues by Category
Performance (2)
⚠️ tyk-configuration-reference/redis-cluster-sentinel.mdx:350 - The documentation fortoken_refresh_before_expirylacks guidance on choosing a safe and efficient value. A very small value (e.g., under a minute) is risky as it leaves little time for the refresh operation to complete, potentially causing connection failures. A very large value (e.g.,30m) will cause more frequent token refreshes than necessary, increasing load on the IAM provider and potentially leading to rate limiting.⚠️ tyk-identity-broker/standalone-tib.mdx:227 - The documentation forIAMAuth.TokenRefreshBeforeExpirylacks guidance on choosing a safe and efficient value. A very small value (e.g., under a minute) is risky as it leaves little time for the refresh operation to complete, potentially causing connection failures. A very large value (e.g.,30m) will cause more frequent token refreshes than necessary, increasing load on the IAM provider and potentially leading to rate limiting.
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check warning on line 350 in tyk-configuration-reference/redis-cluster-sentinel.mdx
probelabs / Visor: performance
performance Issue
The documentation for `token_refresh_before_expiry` lacks guidance on choosing a safe and efficient value. A very small value (e.g., under a minute) is risky as it leaves little time for the refresh operation to complete, potentially causing connection failures. A very large value (e.g., `30m`) will cause more frequent token refreshes than necessary, increasing load on the IAM provider and potentially leading to rate limiting.
Raw output
Add guidance on the trade-offs of this setting and recommend a safe range. For example: 'The default of `5m` is recommended for most use cases. This value should be large enough to accommodate network latency and retries during the refresh process. Setting it below one minute is not recommended. Values larger than `15m` may result in excessive API calls to the identity provider.'
Check warning on line 227 in tyk-identity-broker/standalone-tib.mdx
probelabs / Visor: performance
performance Issue
The documentation for `IAMAuth.TokenRefreshBeforeExpiry` lacks guidance on choosing a safe and efficient value. A very small value (e.g., under a minute) is risky as it leaves little time for the refresh operation to complete, potentially causing connection failures. A very large value (e.g., `30m`) will cause more frequent token refreshes than necessary, increasing load on the IAM provider and potentially leading to rate limiting.
Raw output
Add guidance on the trade-offs of this setting and recommend a safe range. For example: 'The default of `5m` is recommended for most use cases. This value should be large enough to accommodate network latency and retries during the refresh process. Setting it below one minute is not recommended. Values larger than `15m` may result in excessive API calls to the identity provider.'
Loading