Merging to release-5.3: [DX-1398] Update tyk-pump-dashboard-config.md (#5078)

[buger]

User description

DX-1398 Update tyk-pump-dashboard-config.md (#5078)

Update tyk-pump-dashboard-config.md

---

PR Type

Documentation

---

Description

• Updated the Tyk Dashboard configuration documentation to reflect changes in the configuration structure.
• Replaced the sql, sql_aggregate, and uptime_pump_config sections with a unified storage section.
• Added new subsections main, analytics, logs, and uptime under the storage section, each with table_sharding configuration.

---

Changes walkthrough 📝

	Relevant files
Documentation	tyk-pump-dashboard-config.md Update Tyk Dashboard configuration structure for table sharding tyk-docs/content/tyk-pump/tyk-pump-configuration/tyk-pump-dashboard-config.md Updated configuration structure for Tyk Dashboard. Replaced sql, sql_aggregate, and uptime_pump_config with storage sections. Added main, analytics, logs, and uptime under storage. +18/-18

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Enhancement	Centralize the table_sharding configuration to reduce redundancy It appears that the table_sharding configuration is repeated across multiple sections (main, analytics, logs, uptime). If table_sharding is intended to have the same setting across these different storage types, consider centralizing this configuration to reduce redundancy and simplify future updates. tyk-docs/content/tyk-pump/tyk-pump-configuration/tyk-pump-dashboard-config.md [441-457] "storage": { + "default_settings": { + "table_sharding": true + }, "main": { ... - "table_sharding": true }, "analytics": { ... - "table_sharding": true }, "logs": { ... - "table_sharding": true }, "uptime": { ... - "table_sharding": true } }, Suggestion importance[1-10]: 8 Why: The suggestion to centralize the table_sharding configuration is logical and improves maintainability by reducing redundancy. This change simplifies future updates and ensures consistency across different storage types.	8

[netlify]

✅ PS. Pls add /docs/nightly to the end of url

Name	Link
🔨 Latest commit	217964f
🔍 Latest deploy log	https://app.netlify.com/sites/tyk-docs/deploys/669f739820ae640008bd6601
😎 Deploy Preview	https://deploy-preview-5112--tyk-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ PS. Pls add /docs/nightly to the end of url

Name	Link
🔨 Latest commit	217964f
🔍 Latest deploy log	https://app.netlify.com/sites/tyk-docs/deploys/669f739820ae640008bd6601
😎 Deploy Preview	https://deploy-preview-5112--tyk-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.