fix:[PLG-576] Wiz collector failed to trigger as a part of scheduler

[akashpaladin]

PLG-576

Description

Wiz collector failed to trigger as a part of scheduler

Problem

Solution

added wiz to config

Fixes # (issue if any)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Chore (no code changes)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also
list any relevant details for your test configuration

• Test A
• Test B

Checklist:

• My code follows the style guidelines of this project
• My commit message/PR follows the contribution guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Other Information:

List any documentation updates that are needed for the Wiki

Summary by CodeRabbit

• New Features
  • Added support for the wiz plugin in the plugin configuration settings.

[coderabbitai]

Walkthrough

The update involves modifying a SQL query in the DB.sql file to include the wiz plugin in the pac_config_properties table. This ensures the wiz plugin is now part of the plugin-related configurations, enhancing the system's capability to handle this additional plugin.

Changes

File Path	Change Summary
installer/resources/pacbot_app/files/DB.sql	Updated the SQL query to include the wiz plugin in the pac_config_properties table for plugin configurations.

Poem

In the realm of code so bright,
A plugin named wiz takes flight,
Joining comrades, old and new,
Enhancing tasks they all pursue.
SQL whispers, "Welcome, friend,"
Together, their powers blend.
🌟✨🐇

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8cc000d and 85707ff.

Files selected for processing (1)

• installer/resources/pacbot_app/files/DB.sql (1 hunks)

Additional comments not posted (1)

installer/resources/pacbot_app/files/DB.sql (1)

3125-3125: The SQL update to include the wiz plugin looks correct.

Verification successful

---

The addition of 'wiz' in the DB.sql file appears consistent with other plugins and does not introduce any conflicts.

• The term 'wiz' is used in a WHERE clause alongside other plugins.
• It is included in an UPDATE statement setting the application for enabled plugins.
• The INSERT statement modification to include 'wiz' is consistent with these usages.

Scripts executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify that the addition of 'wiz' does not conflict with existing plugins.

# Test: Search for 'wiz' in other SQL files to ensure no conflicts.
rg --type sql $'wiz' --files-with-matches

Length of output: 84

---

---

Script:

#!/bin/bash
# Extract all lines containing 'wiz' in the DB.sql file to review its usage and ensure no conflicts.
rg 'wiz' installer/resources/pacbot_app/files/DB.sql

Length of output: 1157