Removed unused fields

[tisnik]

Description

Removed unused fields

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

Summary by CodeRabbit

• Documentation
  • Simplified example configurations by removing deprecated user data collection settings, reducing setup complexity.
  • Clarified that the default authentication remains set to “noop,” with no functional changes.
  • Updated examples to align with current behavior and prevent misconfiguration.

[coderabbitai]

Walkthrough

Removed the data_collector block from user_data_collection in two example YAML configurations. Authentication remains set to module: "noop". No other changes.

Changes

Cohort / File(s)	Summary
Example configs: remove data_collector examples/lightspeed-stack-lls-external.yaml, examples/lightspeed-stack-lls-library.yaml	Deleted user_data_collection.data_collector block (enabled, ingress_server_url, ingress_server_auth_token, ingress_content_service_name, collection_interval, cleanup_after_send, connection_timeout_seconds). Authentication module unchanged ("noop").

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I nibbled the configs, neat and small,
Snipped the collector—no crumbs at all.
Auth stays “noop,” a quiet tune,
Two files tidied by the moon.
Thump-thump! My paws approve the sweep—
Less clutter now, and cleaner leap.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

examples/lightspeed-stack-lls-external.yaml (1)

18-19: Clarify noop auth usage

• In examples/lightspeed-stack-lls-external.yaml (lines 18–19), either remove the entire authentication block (given auth_enabled: false) or append a comment noting that module: "noop" is a dev-only placeholder.
• Verification ran: no occurrences of any removed data_collector keys remain.

examples/lightspeed-stack-lls-library.yaml (1)

18-18: LGTM; mirrors external example. Consider same clarification note

This matches the external example; same note about removing or commenting the noop auth block in a disabled-auth config to avoid confusion.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between f8da8e0 and dee5b3d.

📒 Files selected for processing (2)

• examples/lightspeed-stack-lls-external.yaml (1 hunks)
• examples/lightspeed-stack-lls-library.yaml (1 hunks)

⏰ 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). (2)

• GitHub Check: build-pr
• GitHub Check: e2e_tests