[fix] Remove Discord webhook implementation

[nwithan8]

Discord webhook implementation is inconsistent and requires a number of assumptions and specific configuration conditions that are best left to downstream implementations.

The base TautulliWebhook class and TautulliWebhookTrigger enum remain here, usable for downstream implementations

Summary by CodeRabbit

• Chores
  • Updated .gitignore to exclude the reference/ directory from version control.
  • Simplified import structure by removing unused Discord webhook-related imports.
  • Renamed _TautulliWebhook class to TautulliWebhook, making it publicly accessible.
  • Removed the discord.py file, eliminating Discord webhook handling functionality.

These changes streamline the codebase, improving maintainability and clarity.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The changes in this pull request involve modifications to several files related to Tautulli webhooks. The .gitignore file has been updated to exclude the reference/ directory. In the tautulli/tools/webhooks/__init__.py file, multiple unused import statements related to Discord webhooks have been removed to simplify the import structure. The tautulli/tools/webhooks/base.py file has seen a class renaming from _TautulliWebhook to TautulliWebhook, making it a public class. Lastly, the tautulli/tools/webhooks/discord.py file has been deleted, removing several classes and functionality associated with Discord webhooks.

Changes

File Path	Change Summary
.gitignore	Added entry to ignore the reference/ directory.
tautulli/tools/webhooks/init.py	Removed multiple unused import statements related to Discord webhooks.
tautulli/tools/webhooks/base.py	Renamed class _TautulliWebhook to TautulliWebhook, making it a public class while retaining its functionality.
tautulli/tools/webhooks/discord.py	Deleted file, removing classes and functionality for handling Discord webhooks.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant WebhookHandler
    participant BaseModel

    User->>WebhookHandler: Send Webhook Request
    WebhookHandler->>BaseModel: Validate Request
    BaseModel-->>WebhookHandler: Return Validation Result
    WebhookHandler->>User: Send Response

Loading

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 26d4e59 and 382a0a0.

📒 Files selected for processing (4)

• .gitignore (1 hunks)
• tautulli/tools/webhooks/__init__.py (1 hunks)
• tautulli/tools/webhooks/base.py (1 hunks)
• tautulli/tools/webhooks/discord.py (0 hunks)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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