3 Commits (b304ee495dd8b27b1effb63dc6b4772b4e409a9d)

Author	SHA1	Message	Date
Matt Farina	e711488970	Move pkg/release to pkg/release/v1 to support v3 charts ... This is part of HIP 20 which provides a means to have v3 charts that live alongside v2 charts while having breaking changes. The plan is to have a different release object for v3 chart instances for at least a couple reasons: 1. So that the chart object on the release can be fundamentally different. 2. So that Helm v3 does not detect or try to work with instances of charts whose apiVersion it does not know about. Note: it is expected that Helm v3 usage will be used long after the Helm project no longer supports it. 5 years after Helm v2 had reached end-of-life there was still usage of it. Note: The release util package is separate from the versioned elements as it is planned to use generics to handle multiple release object versions. Signed-off-by: Matt Farina <matt.farina@suse.com>	12 months ago
Matt Farina	61d3eca55c	Move pkg/chart to pkg/chart/v2 to prepare for v3 charts ... This change moves the code, updates the import locations, and adds a doc.go file to document what the v2 package is for. This is part of HIP 20 for v3 charts Signed-off-by: Matt Farina <matt.farina@suse.com>	12 months ago
Matt Farina	18ca7c1002	Move pkg/releaseutil to pkg/release/util ... The releaseutil package was originally designed to work against a generated codebase from a protobuf in Helm v2. This is when Helm used gRPC to communicate to a server side component named Tiller. When Helm moved everything client side, this package remained and it supported the release package. This change moves releaseutil to be a sub-packge of release. This is part of the change to support apiVersion v3 charts which is documented in HIP 20 Signed-off-by: Matt Farina <matt.farina@suse.com>	12 months ago