Update BYOP documentation to reflect "Clusters" terminology#762
Conversation
…hared vs account cluster details.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates the BYOP reverse-proxy documentation to align with current dashboard UI and API terminology. BYOP proxies are now documented as appearing under Reverse Proxy > Clusters as account clusters, with a new section distinguishing shared and account cluster behaviors. Setup instructions, prerequisites, wizard navigation, screenshot alt texts, and API verification steps are all updated accordingly. ChangesBYOP Proxy Documentation Terminology and Navigation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Update BYOP documentation to reflect "Clusters" terminology and add shared vs account cluster details.
Summary by CodeRabbit