helm search hub should optionally return the repo URL as part of the results

[omkensey]

It would be nice if helm search hub could give the URL of the repo (not necessarily by default, but as an optional column/JSON key), so as to avoid a roundtrip to the Hub description page for the actual repo URL if I can tell from the search listings which chart repo I want.

[SimonHeimberg]

The hub server returns the information, only cli needs adaption.

So a possible work around (when searching "rancher server"):
curl https://hub.helm.sh/api/chartsvc/v1/charts/search?q=rancher+server | json_pp
The repo url is in key url in repo (data[...].attributes.repo.url).
(json_pp is optional. It pretty prints json, which helps me to read it.)

[bacongobbler]

This is a great suggestion, @omkensey. I think adding another field to the table output displaying the repository URL would be a welcome change.

A little bit of context here: The idea with helm search hub returning that URL was that the chart repository maintainers were looking to add support to use that URL as input to helm install, like so:

><> helm search hub wordpress --max-col-width 0 | tail -n 1
https://hub.helm.sh/charts/bitnami/wordpress           	9.1.1        	5.3.2      	Web publishing platform for building blogs and websites.

then:

><> helm install wordpress https://hub.helm.sh/charts/bitnami/wordpress

cc'ing @mattfarina as he may have more context on where we are with that particular feature.

Adding the repository URL to the table output would be good as well. More options are better :)

[SimonHeimberg]

A little bit of context here: ...

Thank you. I did not see this in the doc. Now I found it in docs/intro/using_helm since I knew what to look for.

[tharun208]

I like to work on this

[mattfarina]

I like the idea of adding the column. I would also like to see ><> helm install wordpress https://hub.helm.sh/charts/bitnami/wordpress work. This might be something to add into the Artifact Hub as well.

[scottrigby]

I like both of these ideas::

1. optional flag (--list-repo or something)
2. updating Artifact Hub to allow installing directly from paths like https://artifacthub.io/packages/helm/bitnami/etcd (curl https://hub.helm.sh/api/chartsvc/v1/charts/search?q=etcd)

How would idea 2 ideally work though? Maybe under the hood something like helm install option 5 (By chart reference and repo url: helm install --repo https://example.com/charts/mynginx nginx), grabbing chart name by splitting second part of monocular search API r.id (etcd from bitnami/etcd)?

[github-actions]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.