goharbor / goharbor/harbor

MAVEN_CENTRAL_URL to harbor.yml trivy config

Open
#17,530 0 comments 1 reaction 1 assignee Claimed by @zyyw View on GitHub
area/configuration area/vulnerability-scan kind/requirement
Dominant language
Go
Stars
29.4k
Forks
5.3k
Avg merge
4d 2h
Merged PRs (30d)
71

Description

**Describe the solution you'd like**
In our business scenario, we configured Trivy with maven proxy (as described on official Trivy troubleshooting https://aquasecurity.github.io/trivy/v0.25.4/docs/references/troubleshooting/) to both caching and throttling and it works like a charm.
In order to do it, it's necessary to **manually** add the MAVEN_CENTRAL_URL env to trivy config environment.

My simple proposal is to add a new key "trivy.maven_central_url" inside harbor.yml which if is not empty it should auto add to trivy env the MAVEN_CENTRAL_URL variable.
If "trivy.maven_central_url" empty or not configured NOT add anything to trivy env. This param should be also managed inside migration script.

The main reason of this proposal is portability mainly during update process, right now we need to remember to manually add MAVEN_CENTRAL_URL to trivy env config because migration script is not caring about it yet.

Thanks!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.