Skip to content

LCORE-1356: Regenerated doc#1809

Merged
tisnik merged 1 commit into
lightspeed-core:mainfrom
tisnik:lcore-1356-regenerated-doc-
May 28, 2026
Merged

LCORE-1356: Regenerated doc#1809
tisnik merged 1 commit into
lightspeed-core:mainfrom
tisnik:lcore-1356-regenerated-doc-

Conversation

@tisnik
Copy link
Copy Markdown
Contributor

@tisnik tisnik commented May 28, 2026

Description

LCORE-1356: Regenerated doc

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up service version
  • Bump-up dependent library
  • Bump-up library or tool used for development (does not change the final image)
  • CI configuration change
  • Konflux configuration change
  • Unit tests improvement
  • Integration tests improvement
  • End to end tests improvement
  • Benchmarks improvement

Tools used to create PR

  • Assisted-by: N/A
  • Generated by: N/A

Related Tickets & Documents

  • Related Issue #LCORE-1356

Summary by CodeRabbit

Documentation

  • Extended configuration schema documentation to support human-in-the-loop approval controls with granular approval filters for tool invocations.
  • Added documentation for neural reranking configuration enabling cross-encoder-based result optimization.
  • Added documentation for agent skills configuration with validated skill directory management.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 28, 2026

Walkthrough

Configuration 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.

Changes

Configuration Schema Documentation

Layer / File(s) Summary
Approval filter and configuration schemas
docs/config.html, docs/config.json, docs/config.md
ApprovalFilter and ApprovalsConfiguration schemas added with granular tool-approval control; approvals property integrated into Configuration schema; require_approval field (supporting always, never, or ApprovalFilter) added to ModelContextProtocolServer.
Reranker configuration schema
docs/config.html, docs/config.json, docs/config.md
RerankerConfiguration schema introduced with enabled and model fields for cross-encoder-based RAG reranking; reranker property integrated into top-level Configuration.
Skills configuration schema
docs/config.html, docs/config.json, docs/config.md
SkillsConfiguration schema added with paths array for skill directories and startup validation; nullable skills property integrated into Configuration schema.
PostgreSQL configuration enhancements
docs/config.json
SSL mode enum expanded and gss_encmode field added to PostgreSQLDatabaseConfiguration.
Global configuration table extension
docs/config.html
Configuration schema table extended with additional top-level fields including newly introduced reranker and skills alongside existing entries.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • jrobertboos
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'LCORE-1356: Regenerated doc' is vague and does not clearly describe the specific configuration changes introduced in the pull request. Consider using a more specific title that describes the actual changes, such as 'Add approval filters, reranking, and skills configuration to documentation' or similar.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
✨ Simplify code
  • Create PR with simplified 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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between 397acf1 and 2526fcd.

📒 Files selected for processing (3)
  • docs/config.html
  • docs/config.json
  • docs/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

Comment thread docs/config.md
| 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. |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

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.

Suggested change
| 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.

@tisnik tisnik merged commit 8b54312 into lightspeed-core:main May 28, 2026
31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant