fix(ci): Fix oras command not found error

[Tiryoh]

the latest ubuntu image has been updated and "oras" command not found in the new image

Summary by CodeRabbit

• Chores
  • Updated the workflow to include a new setup step for the ORAS tool, enhancing the environment for vulnerability database operations.

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow file .github/workflows/update-trivy-cache.yaml by adding a new step to set up the ORAS tool within the update-trivy-db job. This new step is implemented using the oras-project/setup-oras@v1 action and is placed at the beginning of the job's steps. The existing steps for downloading and extracting the vulnerability database, as well as the Java database, are unchanged, and the caching mechanism for the databases remains intact.

Changes

File Path	Change Summary
.github/workflows/update-trivy-cache.yaml	Added new step for setting up ORAS tool in update-trivy-db job.

Possibly related PRs

• chore(ci): Save Trivy cache to avoid Trivy TOOMANYREQUESTS errors #182: Introduces a new GitHub Actions workflow file for updating the Trivy cache, directly related to the modifications in the main PR.
• chore(ci): Use Trivy cache #183: Modifies the GitHub Actions workflow to include environment variables affecting the Trivy scanner's execution, relevant to the context of the main PR.

Poem

In the garden where we play,
A new tool joins the fray today.
ORAS sets the stage so bright,
Caches stored, all feels just right.
Hop along, let’s cheer and sing,
For updates bring a joyful spring! 🐇✨

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

.github/workflows/update-trivy-cache.yaml (2)

14-15: LGTM! This change addresses the PR objective.

The addition of the ORAS setup step effectively resolves the "oras command not found" error mentioned in the PR description. This is a good solution that ensures the ORAS tool is available for subsequent steps in the workflow.

Consider using a more specific version of the action for better reproducibility. For example:

uses: oras-project/setup-oras@v1.1.0

This ensures that future updates to the v1 major version don't unexpectedly change the workflow behavior.

---

Line range hint 1-48: Overall, the changes effectively address the PR objective without disrupting the existing workflow.

The addition of the ORAS setup step at the beginning of the job ensures that the oras command is available for all subsequent steps. This change:

1. Resolves the "oras command not found" error.
2. Integrates seamlessly with the existing workflow structure.
3. Maintains the functionality of downloading, extracting, and caching the Trivy and Java databases.

The rest of the workflow remains unchanged, preserving the daily update schedule, manual trigger option, and efficient caching mechanism.

To further improve the workflow, consider:

1. Adding error handling or retry mechanisms for the ORAS pull and copy operations.
2. Implementing version pinning for the database images to ensure consistency across runs.
3. Adding a step to verify the integrity of the downloaded databases.

These suggestions could enhance the reliability and security of the workflow.

🧰 Tools

🪛 actionlint

19-19: shellcheck reported issue in this script: SC2086:info:1:36: Double quote to prevent globbing and word splitting

(shellcheck)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between e068704 and de0d6e3.

📒 Files selected for processing (1)

• .github/workflows/update-trivy-cache.yaml (1 hunks)

🧰 Additional context used