Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: handle trivy insecure database in ClientServer mode #1623

Merged
merged 1 commit into from
Nov 8, 2023

Conversation

miecio45
Copy link
Contributor

@miecio45 miecio45 commented Nov 7, 2023

Description

This will allow trivy.dbRepositoryInsecure: "true" setting to work also in ClienServer mode. Useful for javaDbRepository which is (AFAIK) not stored on Server

Related issues

Checklist

  • I've read the guidelines for contributing to this repository.
  • I've added tests that prove my fix is effective or that my feature works.
  • I've updated the documentation with the relevant information (if needed).
  • I've added usage information (if the PR introduces new options)
  • I've included a "before" and "after" example to the description (if the PR is a user interface change).

@miecio45 miecio45 requested a review from chen-keinan as a code owner November 7, 2023 17:08
@CLAassistant
Copy link

CLAassistant commented Nov 7, 2023

CLA assistant check
All committers have signed the CLA.

@miecio45 miecio45 changed the title Handle trivy insecure database in ClientServer mode fix: handle trivy insecure database in ClientServer mode Nov 7, 2023
@github-actions github-actions bot added the bug label Nov 7, 2023
@chen-keinan
Copy link
Contributor

@miecio45 lgtm 🚀 thank you for the contribution

@chen-keinan chen-keinan merged commit 95a7f1f into aquasecurity:main Nov 8, 2023
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Handle dbRepositoryInsecure in client-server trivy scenario
3 participants