Skip to content

[TT-17611] IAM authentication for Google Cloud - #2766

Merged
sharadregoti merged 17 commits into
docs-5.15from
tt17611-iam-auth
Aug 27, 2026
Merged

[TT-17611] IAM authentication for Google Cloud#2766
sharadregoti merged 17 commits into
docs-5.15from
tt17611-iam-auth

Merge main into tt17611-iam-auth

cf526af
Select commit
Loading
Failed to load commit list.
probelabs / Visor: quality succeeded Aug 26, 2026 in 1m 31s

✅ Check Passed (Warnings Found)

quality 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

Documentation (1)

  • ⚠️ tyk-configuration-reference/redis-cluster-sentinel.mdx:404 - The example configuration for IAM with a Redis Cluster (enable_cluster: true) uses host and port fields. This contradicts the guidance in the "Configure Redis Cluster" section of the same document, which specifies using the addrs field for cluster configurations. This inconsistency can lead to user confusion and misconfiguration.

Powered by Visor from Probelabs

💡 TIP: You can chat with Visor using /visor ask <your question>

Annotations

Check warning on line 405 in tyk-configuration-reference/redis-cluster-sentinel.mdx

See this annotation in the file changed.

@probelabs probelabs / Visor: quality

documentation Issue

The example configuration for IAM with a Redis Cluster (`enable_cluster: true`) uses `host` and `port` fields. This contradicts the guidance in the "Configure Redis Cluster" section of the same document, which specifies using the `addrs` field for cluster configurations. This inconsistency can lead to user confusion and misconfiguration.
Raw output
To ensure consistency with the Redis Cluster configuration guidance, modify the example to use the `addrs` field instead of `host` and `port`. Even for a single discovery endpoint, it should be presented as a list item within `addrs`.