Skip to content

Conversation

@StFS
Copy link
Contributor

@StFS StFS commented Aug 1, 2025

This PR adds the ability to provide a custom message in the slack output. This is useful for example if you want to include the environment name or something similar.

@coderabbitai
Copy link

coderabbitai bot commented Aug 1, 2025

Walkthrough

A new optional field, slack_title, was added to the configuration model and CLI interface to allow customization of Slack message titles. The runner logic now uses this field, if set, when posting Slack messages. No other logic, validation, or control flow was changed.

Changes

Cohort / File(s) Change Summary
Config Model Update
robusta_krr/core/models/config.py
Added an optional slack_title string field to the Config class.
Runner Slack Message Title
robusta_krr/core/runner.py
Modified _process_result to use settings.slack_title for Slack message title if provided; otherwise, defaults to the previous string.
CLI Option for Slack Title
robusta_krr/main.py
Introduced a new --slacktitle CLI option to set slack_title in Config, with help text and integration into the "Output Settings" help panel.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI (main.py)
    participant Config
    participant Runner

    User->>CLI (main.py): Run command with --slacktitle
    CLI (main.py)->>Config: Pass slack_title to Config
    Runner->>Config: Access slack_title
    Runner->>Slack: Post message with slack_title (if set)
Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 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
🪧 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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai 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

Documentation and Community

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

Copy link

@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: 0

🧹 Nitpick comments (3)
robusta_krr/core/models/config.py (1)

73-73: Add minimal validation & description for slack_title

The field works as-is, but adding a description and trimming/ignoring blank strings prevents accidental empty Slack titles.

-slack_title: Optional[str] = pd.Field(None)
+slack_title: Optional[str] = pd.Field(
+    default=None,
+    description="Custom title for the Slack message. Falls back to a default when None or empty.",
+)
+
+@pd.validator("slack_title")
+def _validate_slack_title(cls, v: Optional[str]) -> Optional[str]:
+    # Treat whitespace-only values as not provided
+    if v is not None and not v.strip():
+        return None
+    return v
robusta_krr/core/runner.py (1)

160-165: Handle "*" namespace to generate clearer Slack titles

When settings.namespaces == "*", ' '.join(settings.namespaces) returns "*", which is technically fine but not very descriptive. A small refactor improves readability.

-channel = settings.slack_output if settings.slack_output.startswith('#') else f"#{settings.slack_output}"
-slack_title = settings.slack_title if settings.slack_title else f'Kubernetes Resource Report for {(" ".join(settings.namespaces))}'
+channel = settings.slack_output if settings.slack_output.startswith('#') else f"#{settings.slack_output}"
+namespaces_str = "all namespaces" if settings.namespaces == "*" else " ".join(settings.namespaces)
+slack_title = settings.slack_title or f"Kubernetes Resource Report for {namespaces_str}"
robusta_krr/main.py (1)

269-274: Minor UX polish for --slacktitle

Consider:

  1. Adding a short alias (-T) in line with other options.
  2. Updating the help text to align with the actual default (<namespaces> rather than <environment>).

These tweaks keep the CLI consistent and self-explanatory.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 90cbfc8 and 1f11b9f.

📒 Files selected for processing (3)
  • robusta_krr/core/models/config.py (1 hunks)
  • robusta_krr/core/runner.py (1 hunks)
  • robusta_krr/main.py (2 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
robusta_krr/core/runner.py (1)
robusta_krr/core/integrations/kubernetes/__init__.py (1)
  • namespaces (54-87)
🔇 Additional comments (1)
robusta_krr/main.py (1)

364-365: Wiring looks correct

The new CLI option is correctly forwarded into the Config, ensuring end-to-end support.

Copy link
Contributor

@arikalon1 arikalon1 left a comment

Choose a reason for hiding this comment

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

nice work

Thanks for the PR @StFS

@arikalon1 arikalon1 merged commit dc45130 into robusta-dev:main Aug 1, 2025
2 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.

2 participants