[TT-17611] IAM authentication for Google Cloud - #2766
Merged
probelabs / Visor: architecture
failed
Aug 21, 2026 in 30s
🚨 Check Failed
architecture check failed because fail_if condition was met.
Details
📊 Summary
- Total Issues: 3
- Error Issues: 2
- Warning Issues: 1
🔍 Failure Condition Results
Failed Conditions
- global_fail_if: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
- Severity: ❌ error
Issues by Category
Documentation (2)
- ❌ tyk-configuration-reference/redis-cluster-sentinel.mdx:369 - The documentation for Tyk MDCB's IAM configuration is contradictory. It first states that
iam_authis nested in thestorageblock for MDCB, but a later list of valid locations omits thestorageblock, only mentioninganalytics_storage. This inconsistency could prevent users from correctly configuring IAM for their primary MDCB Redis connection, as the correct location is not clearly documented. ⚠️ tyk-identity-broker/standalone-tib.mdx:205 - The documentation overstates the feature's capability by stating it works with any "cloud-managed Redis or Valkey instance". The feature is currently limited to specific Google Cloud services (Memorystore for Valkey and Memorystore for Redis Cluster). This broad statement could mislead users into assuming support for other cloud providers (like AWS or Azure) or unsupported Google Cloud services, which would fail at runtime.
Logic (1)
- ❌ system:0 - Global failure condition met: output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check failure on line 369 in tyk-configuration-reference/redis-cluster-sentinel.mdx
probelabs / Visor: architecture
documentation Issue
The documentation for Tyk MDCB's IAM configuration is contradictory. It first states that `iam_auth` is nested in the `storage` block for MDCB, but a later list of valid locations omits the `storage` block, only mentioning `analytics_storage`. This inconsistency could prevent users from correctly configuring IAM for their primary MDCB Redis connection, as the correct location is not clearly documented.
Raw output
Update the list of valid locations for the `iam_auth` block in Tyk MDCB to include the `storage` block, resolving the contradiction. The line should explicitly mention both `storage` and `analytics_storage` as valid parent blocks for the IAM configuration.
Check warning on line 205 in tyk-identity-broker/standalone-tib.mdx
probelabs / Visor: architecture
documentation Issue
The documentation overstates the feature's capability by stating it works with any "cloud-managed Redis or Valkey instance". The feature is currently limited to specific Google Cloud services (Memorystore for Valkey and Memorystore for Redis Cluster). This broad statement could mislead users into assuming support for other cloud providers (like AWS or Azure) or unsupported Google Cloud services, which would fail at runtime.
Raw output
To prevent user confusion and failed setup attempts, narrow the description to specify the currently supported services. The text should explicitly mention "Google Cloud Memorystore for Valkey and Memorystore for Redis Cluster" and clarify that other services are not supported.
Loading