-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
helm search hub should optionally return the repo URL as part of the results #7419
Comments
The hub server returns the information, only cli needs adaption. So a possible work around (when searching "rancher server"): |
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
then:
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 :) |
Thank you. I did not see this in the doc. Now I found it in |
I like to work on this |
I like the idea of adding the column. I would also like to see |
I like both of these ideas::
How would idea 2 ideally work though? Maybe under the hood something like |
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. |
The flag makes helm print the chart repo URL to use with helm repo add. Issue: helm#7419 Signed-off-by: Dmitriy Ermakov <demonihin@gmail.com>
The flag makes helm print the chart repo URL to use with helm repo add. Issue: helm#7419 Signed-off-by: Dmitriy Ermakov <demonihin@gmail.com>
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.The text was updated successfully, but these errors were encountered: