Often times the option is only required to get helm to download the missing dependencies. And then it will only be required the next time a dependency is actually updated.
Proposal:
Implement a caching mechanism, which can be added in addition to the current flag, so that the command is only really executed if some/all of the dependencies are missing locally. Something like --cache-dependencies. This would maintain the current default behavior.
Users can force cache-invalidation by
a) temporarily loosing the --cache-dependencies option or
b) by clearing the downloaded dependencies from disk.
Since dependencies are never checked into version control, CI systems could always start with a cold cache. Therefore circumventing the issue of when to invalidate the CI cache.
Often times the option is only required to get
helmto download the missing dependencies. And then it will only be required the next time a dependency is actually updated.Proposal:
Implement a caching mechanism, which can be added in addition to the current flag, so that the command is only really executed if some/all of the dependencies are missing locally. Something like
--cache-dependencies. This would maintain the current default behavior.Users can force cache-invalidation by
a) temporarily loosing the
--cache-dependenciesoption orb) by clearing the downloaded dependencies from disk.
Since dependencies are never checked into version control, CI systems could always start with a cold cache. Therefore circumventing the issue of when to invalidate the CI cache.