docs: refactor shared gateway and CA guidance - #6966
Conversation
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis documentation update adds dedicated guides for shared inference gateway routes and corporate CA trust. Existing inference, command, troubleshooting, changelog, and navigation pages now link to the new guides and provide shorter cross-references. ChangesShared Gateway Routes
Corporate CA Trust
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
🌿 Preview your docs: https://nvidia-preview-pr-6966.docs.buildwithfern.com/nemoclaw |
PR Review Advisor — InformationalAdvisor assessment: Informational / high confidence Model lanes
Nemotron output stays in workflow artifacts and does not change the assessment above. E2E guidanceAdvisory only. E2E / PR Gate selects and runs jobs independently. Recommended E2E: 3 optional E2E recommendations
This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge. |
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/inference/use-shared-gateway-routes.mdx`:
- Around line 59-61: Update the recovery guidance in the affected sandbox
troubleshooting bullets to explicitly require removing the sandbox after backing
it up and before re-onboarding, particularly for incomplete legacy custom-route
metadata and invalid gateway bindings. Keep the existing backup and
re-onboarding instructions, while matching the removal requirement documented in
the troubleshooting reference.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: cdb7a365-47a0-494b-b46f-a79b0969ed3a
📒 Files selected for processing (10)
docs/changelog/2026-07-10.mdxdocs/changelog/2026-07-14.mdxdocs/index.ymldocs/inference/switch-models.mdxdocs/inference/switch-providers.mdxdocs/inference/use-shared-gateway-routes.mdxdocs/inference/view-active-inference-route.mdxdocs/reference/commands.mdxdocs/reference/troubleshooting.mdxdocs/security/configure-corporate-ca-trust.mdx
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
prekshivyas
left a comment
There was a problem hiding this comment.
Reviewed the documentation refactor and latest recovery-guidance fix. Internal links, published Fern routes, generated agent variants, and strict docs validation pass; head-specific E2E checks are green. Approving.
Summary
Consolidates shared gateway route behavior into a focused Manage Inference page and corporate CA behavior into a focused Security page. Troubleshooting remains one searchable reference with concise recovery entries and preserved anchors, while agent-specific guidance reflects the tested support matrix.
Changes
Type of Change
Quality Gates
Verification
Signed-off-by:line and every commit appears asVerifiedin GitHubpre-commit,commit-msg, andpre-pushhooks passed, ornpm run check:diffpassed when hooks were skipped or unavailablenpx vitest run test/check-docs-published-routes.test.ts test/check-docs-links.test.ts test/changelog-docs.test.ts(40 passed)npm testfor broad runtime/test-harness changes;npm run checkfor repo-wide validation/coverage changes — command/result:npm run docsbuilds without warnings (doc changes only)npm run docsexited successfully. Fern reported the unchanged light-theme contrast warning and a remote FDR redirect comparison warning caused by an HTTP 403.Signed-off-by: Miyoung Choi miyoungc@nvidia.com
Summary by CodeRabbit