chore: new update for failing job on new vulnerabilities

[sagar-qa007]

Description

Failing job if new vurn found

Fixes #37036

Automation

/ok-to-test tags=""

🔍 Cypress test results

Caution

If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• New Features

  • Introduced a new workflow step to check for vulnerabilities in Scout and Trivy files, enhancing error handling.
  • Added functionality to generate CSV files for new vulnerabilities detected by Scout and Trivy, improving visibility and reporting.

• Bug Fixes

  • Improved data validation and cleaning processes for vulnerability entries to ensure accuracy.

• Chores

  • Removed outdated functions related to database insertion, streamlining vulnerability processing scripts.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces modifications to enhance vulnerability detection in the GitHub workflow and associated scripts. A new step is added to the workflow to check for new vulnerabilities after running the Scout and Trivy scripts. The scripts themselves have been refactored to replace database insertion logic with functionality that compares detected vulnerabilities against existing entries and generates CSV files for any new vulnerabilities identified.

Changes

File Path	Change Summary
.github/workflows/test-vulnerabilities-data.yml	Added a step to check for new vulnerabilities in Scout and Trivy files, logging results and failing the job if vulnerabilities are found.
scripts/scout_vulnerabilities_data.sh	Removed Docker installation checks; added compare_and_store_vulns function for vulnerability comparison and CSV generation.
scripts/trivy_vulnerabilities_data.sh	Removed database insertion logic; added compare_and_store_vulns function for vulnerability comparison and CSV generation.

Assessment against linked issues

Objective	Addressed	Explanation
Run trivy and scout vulnerabilities scan in GitHub action with image name (#37036)	✅

Possibly related PRs

• chore: Added scout & trivy scan to github workflow #37022: This PR adds vulnerability scanning for Docker images using Scout and Trivy, which directly relates to the changes in the main PR that enhance the workflow for checking vulnerabilities in Scout and Trivy files.
• chore: New schema change for vulnerabilities test #37204: This PR modifies the test-vulnerabilities-data.yml workflow, which is the same file updated in the main PR, focusing on optimizing the handling of vulnerability data and ensuring the integration of vulnerability scans.

Suggested labels

Task, ok-to-test

Suggested reviewers

• sharat87
• abhvsn

🌟 In the realm of code, a change takes flight,
New checks for vulnerabilities, shining bright.
Scout and Trivy now stand guard,
With CSVs to keep the risks barred.
A safer path, we pave today,
In code we trust, come what may! 🌟

---

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

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.