LCORE-1356: Regenerated doc#1809
Conversation
WalkthroughConfiguration schema documentation updated across HTML, JSON, and Markdown formats to add approval controls (ApprovalFilter, ApprovalsConfiguration, require_approval field), neural reranking (RerankerConfiguration), and agent skills (SkillsConfiguration) configurations. PostgreSQL database configuration enhanced with GSS encryption mode field. ChangesConfiguration Schema Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
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/config.md`:
- Line 462: Update the table entry for require_approval so the Type column
explicitly lists the union: `"always" | "never" | ApprovalFilter`; locate the
row with the header/label require_approval in the docs/config.md table and
replace the blank Type cell with that union notation to avoid ambiguity.
🪄 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: ASSERTIVE
Plan: Pro
Run ID: f72c9c54-e97b-45a8-91ee-a55cace01059
📒 Files selected for processing (3)
docs/config.htmldocs/config.jsondocs/config.md
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (13)
- GitHub Check: unit_tests (3.12)
- GitHub Check: unit_tests (3.13)
- GitHub Check: Pyright
- GitHub Check: Pylinter
- GitHub Check: build-pr
- GitHub Check: Konflux kflux-prd-rh02 / lightspeed-stack-on-pull-request
- GitHub Check: E2E Tests for Lightspeed Evaluation job
- GitHub Check: E2E: library mode / ci / group 3
- GitHub Check: E2E: library mode / ci / group 2
- GitHub Check: E2E: server mode / ci / group 1
- GitHub Check: E2E: library mode / ci / group 1
- GitHub Check: E2E: server mode / ci / group 2
- GitHub Check: E2E: server mode / ci / group 3
🔇 Additional comments (3)
docs/config.html (1)
261-322: LGTM!Also applies to: 724-727, 778-788, 1296-1301, 1653-1682, 1814-1844
docs/config.json (1)
133-178: LGTM!Also applies to: 534-538, 602-619, 1053-1069, 1157-1164, 1171-1175, 1369-1388, 1495-1511
docs/config.md (1)
252-253: LGTM!Also applies to: 613-623, 677-695
| | authorization_headers | object | Headers to send to the MCP server. The map contains the header name and the path to a file containing the header value (secret). There are 3 special cases: 1. Usage of the kubernetes token in the header. To specify this use a string 'kubernetes' instead of the file path. 2. Usage of the client-provided token in the header. To specify this use a string 'client' instead of the file path. 3. Usage of the oauth token in the header. To specify this use a string 'oauth' instead of the file path. | | ||
| | headers | array | List of HTTP header names to automatically forward from the incoming request to this MCP server. Headers listed here are extracted from the original client request and included when calling the MCP server. This is useful when infrastructure components (e.g. API gateways) inject headers that MCP servers need, such as x-rh-identity in HCC. Header matching is case-insensitive. These headers are additive with authorization_headers and MCP-HEADERS. | | ||
| | require_approval | string or object | When to require human approval for MCP tool invocations. 'always' requires approval for all tools, 'never' auto-approves all tools (default), or use an ApprovalFilter for granular per-tool control. | | ||
| | require_approval | | When to require human approval for tool invocations. 'always' requires approval for all tools, 'never' auto-approves, or use ApprovalFilter for granular control. | |
There was a problem hiding this comment.
Populate the require_approval type in the table.
The Type column is blank, but this field is a union ("always" | "never" | ApprovalFilter). Please document that explicitly to avoid misconfiguration.
Suggested doc fix
-| require_approval | | When to require human approval for tool invocations. 'always' requires approval for all tools, 'never' auto-approves, or use ApprovalFilter for granular control. |
+| require_approval | string or ApprovalFilter | When to require human approval for tool invocations. 'always' requires approval for all tools, 'never' auto-approves, or use ApprovalFilter for granular control. |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| | require_approval | | When to require human approval for tool invocations. 'always' requires approval for all tools, 'never' auto-approves, or use ApprovalFilter for granular control. | | |
| | require_approval | string or ApprovalFilter | When to require human approval for tool invocations. 'always' requires approval for all tools, 'never' auto-approves, or use ApprovalFilter for granular control. | |
🤖 Prompt for 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.
In `@docs/config.md` at line 462, Update the table entry for require_approval so
the Type column explicitly lists the union: `"always" | "never" |
ApprovalFilter`; locate the row with the header/label require_approval in the
docs/config.md table and replace the blank Type cell with that union notation to
avoid ambiguity.
Description
LCORE-1356: Regenerated doc
Type of change
Tools used to create PR
Related Tickets & Documents
Summary by CodeRabbit
Documentation