🔄 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: quality
succeeded
Aug 24, 2026 in 1m 29s
✅ Check Passed (Warnings Found)
quality 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
Documentation (2)
⚠️ tyk-configuration-reference/kv-store-legacy.mdx:9 - The statement that legacy syntax is "exclusive to Tyk Gateway's configuration" is ambiguous and potentially misleading. It could be interpreted as being valid only in thetyk.conffile, which is incorrect. The following sentence attempts to clarify this for API definitions edited in the Dashboard, but the initial statement is confusing and contradicts the impression given in the Dashboard release notes thatfile://is a supported feature.⚠️ tyk-configuration-reference/kv-store.mdx:71 - The statement "the supported fields in a component's configuration file" is imprecise because it generalizes the behavior of the Tyk Gateway to all other components. According to the table in the 'When References Are Resolved' section, components other than the Gateway support references in any string field, whereas only the Gateway is restricted to a specific list of fields. This initial generalization can cause confusion.
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check warning on line 9 in tyk-configuration-reference/kv-store-legacy.mdx
probelabs / Visor: quality
documentation Issue
The statement that legacy syntax is "exclusive to Tyk Gateway's configuration" is ambiguous and potentially misleading. It could be interpreted as being valid only in the `tyk.conf` file, which is incorrect. The following sentence attempts to clarify this for API definitions edited in the Dashboard, but the initial statement is confusing and contradicts the impression given in the Dashboard release notes that `file://` is a supported feature.
Raw output
Rephrase the sentence to be more precise about what "exclusive" means. The key distinction is which component *resolves* the secret, not where the reference can be written. Clarify that only the Gateway component can resolve this syntax. For example: "This notation is resolved exclusively by the Tyk Gateway component. While you can enter these references into an API definition using the Tyk Dashboard, the Dashboard itself does not resolve them; resolution occurs when the Gateway loads the API definition."
Check warning on line 71 in tyk-configuration-reference/kv-store.mdx
probelabs / Visor: quality
documentation Issue
The statement "the supported fields in a component's configuration file" is imprecise because it generalizes the behavior of the Tyk Gateway to all other components. According to the table in the 'When References Are Resolved' section, components other than the Gateway support references in *any* string field, whereas only the Gateway is restricted to a specific list of fields. This initial generalization can cause confusion.
Raw output
Make the statement more accurate to reflect the different levels of support across components. For example: "References can be used in any string field of an API definition. Support in component configuration files varies: for Tyk Gateway, only a specific set of fields are supported, while for other components like Dashboard and Pump, any string field can contain a reference. See the 'When References Are Resolved' section for full details."
Loading