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

Missing config TRIVY_JAVA_DB_REPOSITORY in trivy.yaml chart template #2271

Open
louzadod opened this issue Sep 26, 2024 · 1 comment · May be fixed by #2272
Open

Missing config TRIVY_JAVA_DB_REPOSITORY in trivy.yaml chart template #2271

louzadod opened this issue Sep 26, 2024 · 1 comment · May be fixed by #2272
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@louzadod
Copy link

What steps did you take and what happened:
I tried to customize JavaDBRepository in my chart and it did not take effect.

[A clear and concise description of what the bug is, and what commands you ran.]
After customizing java db registry and repository in values.yaml, env var TRIVY_JAVA_DB_REPOSITORY was not available for trivy server.

What did you expect to happen:
env var TRIVY_JAVA_DB_REPOSITORY available for trivy server

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Trivy-Operator version (use trivy-operator version): 0.22.0
  • Kubernetes version (use kubectl version): 1.28.11
  • OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): Ubuntu 22.04 LTS
@louzadod louzadod added the kind/bug Categorizes issue or PR as related to a bug. label Sep 26, 2024
louzadod pushed a commit to louzadod/trivy-operator that referenced this issue Sep 26, 2024
louzadod pushed a commit to louzadod/trivy-operator that referenced this issue Sep 26, 2024
@louzadod louzadod linked a pull request Sep 26, 2024 that will close this issue
5 tasks
louzadod added a commit to louzadod/trivy-operator that referenced this issue Sep 26, 2024
Copy link

This issue is stale because it has been labeled with inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and will be auto-closed. label Nov 26, 2024
@afdesk afdesk removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and will be auto-closed. label Nov 27, 2024
@simar7 simar7 added this to the v0.24.0 milestone Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants