-
Notifications
You must be signed in to change notification settings - Fork 13
Core Helm Feature #21
Comments
Plugins are a good test bed for new features before proposing them as a core feature. Long ago, the scope and use case for a feature like Given the amount of community engagement and usage on this plugin over the past few years since initially written, the use case for |
@bacongobbler - I agree in principal with the plugin as a test bed for new features however in this case I have a couple of observations that I'd be interested in you thoughts on? BTW I think this plugin is great and use it extensively in my workflow. Observation 1: I'd assume in general that an outdated command would be a core competency of a package manager. Furthermore with the command as part of the core product it would be possible to evolve the capability to support real pain points, such as notifying users when a chart has been flagged as outdated and moved to a new repo. Observation 2: I'm not sure if the metrics on |
This is something that has to be addressed upstream via helm/helm#7117. Once that work has been implemented by the community, we can look into supporting Windows. As for the original ask, proposing this plugin as a core feature is not something I am interested in moving forward. Thanks for your feedback. |
I recall there being a discussion upstream about implementing |
@bacongobbler this is quite possibly a stupid question but what is the intended Helm flow for update discovery? I think this is even more relevent with the decentralisation of charts, although any solution would only have the configured repos as source. |
|
I don't think I've explained the issue correctly. I'm looking for the Helm equivalent of |
Is there a reason why this isn't a core Helm feature?
The text was updated successfully, but these errors were encountered: