Improve reference docs for InternalProxy#3037
Conversation
Rewrite @description: drop <p> wrappers, make first sentence stand alone, add internal:// URL scheme mention and use-case. Add @yaml showing the shared-auth pattern — internal: validates and injects a downstream X-Api-Key then routes to the real service, with two api: elements on different ports both delegating to it via internal://shared-auth. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 12 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
|
This pull request needs "/ok-to-test" from an authorized committer. |
|
/ok-to-test |
Summary
@description: remove<p>wrappers, sharpen first sentence to stand alone, add theinternal://nameURL scheme and the "shared flow logic" use-case@yamlwith a three-document example showing the realistic shared-auth pattern: aninternal:proxy that injects a downstreamX-Api-Keyand routes to a real service, consumed by twoapi:elements on different portsTest plan
mvn -q -o -pl core compilepasses (verified locally)@yamlis valid YAML (three----separated documents)🤖 Generated with Claude Code