[TT-17611] IAM authentication for Google Cloud - #2766
Merged
probelabs / Visor: architecture
failed
Aug 26, 2026 in 29s
🚨 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
Architecture (2)
⚠️ tyk-configuration-reference/redis-cluster-sentinel.mdx:353 - The configuration for IAM authentication on Tyk Dashboard (redis_iam_authat the top level) is architecturally inconsistent with other components (Gateway, Pump, MDCB) where it is a nestediam_authblock. While this may follow an existing pattern for Dashboard configuration, extending this pattern for a new, cross-component feature introduces unnecessary special-casing and complexity for operators managing a full Tyk stack. A unified configuration structure would be simpler and less error-prone.- ❌ tyk-identity-broker/standalone-tib.mdx:212 - The IAM authentication configuration for Tyk Identity Broker (TIB) uses a different naming convention (PascalCase for the
IAMAuthblock and its fields) compared to all other Tyk components, which use snake_case (iam_auth). Introducing a conflicting naming convention for the same feature within the same product suite is a significant architectural inconsistency. This violates the principle of consistency, increases cognitive load, and makes automation and configuration management more complex and error-prone.
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 warning on line 353 in tyk-configuration-reference/redis-cluster-sentinel.mdx
probelabs / Visor: architecture
architecture Issue
The configuration for IAM authentication on Tyk Dashboard (`redis_iam_auth` at the top level) is architecturally inconsistent with other components (Gateway, Pump, MDCB) where it is a nested `iam_auth` block. While this may follow an existing pattern for Dashboard configuration, extending this pattern for a new, cross-component feature introduces unnecessary special-casing and complexity for operators managing a full Tyk stack. A unified configuration structure would be simpler and less error-prone.
Check failure on line 224 in tyk-identity-broker/standalone-tib.mdx
probelabs / Visor: architecture
architecture Issue
The IAM authentication configuration for Tyk Identity Broker (TIB) uses a different naming convention (PascalCase for the `IAMAuth` block and its fields) compared to all other Tyk components, which use snake_case (`iam_auth`). Introducing a conflicting naming convention for the same feature within the same product suite is a significant architectural inconsistency. This violates the principle of consistency, increases cognitive load, and makes automation and configuration management more complex and error-prone.
Loading