Helm proxy doesn't work for repos with internal relative paths

tmckeag commented 4 years ago

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are you trying to do? We are proxying a helm repository where the repo is relative to some host, and internally charts are relative still to the index location.

For example, assume we are proxying

https://torysinfrastructure/helm

Inside that repo is a chart in a directory appfamily/myapp-1.0.0.tgz, such that the URL to the chart is https://torysinfrastructure/helm/appfamily/myapp-1.0.0.tgz

Therefore, when Nexus proxies this repo, the generated index.yaml for the proxy should refer to the chart as appfamily/myapp-1.0.0.tgz. Today, it reads simply myapp-1.0.0.tgz. The index builder logic in the proxy should respect the relative paths inside the repo.

What feature or behavior is this required for? Helm proxy support.
How could we solve this issue? (Not knowing is okay!) I will attach a PR shortly.
Anything else?

almorgv commented 4 years ago

IMO its a critical issue. Why it has not been fixed yet? We have stuck in this today. This bug makes nexus unusable for numerous helm chart repositories.

LeoQuote commented 4 years ago

mlukaretkyi commented 3 years ago

Related Jira ticket. https://issues.sonatype.org/browse/NEXUS-24682

sonatype-nexus-community / nexus-repository-helm

Helm proxy doesn't work for repos with internal relative paths #127