6 Commits (95a0d2eb89c7d221e8d9fddc19b84e64bc474c8a)

Author	SHA1	Message	Date
Matt Farina	ca8eae9361	Reproducible chart archive builds ... Building the same chart into an archive multiple times will have the same sha256 hash. Perviously, the time in the headers for a file was time.Now() which changed each time. The time is now collected from the operating system when the file is loaded and this time is used. Fixes: #3612 Signed-off-by: Matt Farina <matt.farina@suse.com>	3 months ago
Matt Farina	f80cbe43d0	Moved release objects to enable versioning ... Signed-off-by: Matt Farina <matt.farina@suse.com>	4 months ago
Terry Howe	3e1dd9a5dc	chore: remove pkg/time which is no longer needed ... Signed-off-by: Terry Howe <terrylhowe@gmail.com>	5 months ago
Matt Farina	9dcc49cbd5	Move lint pkg to be part of each chart version ... Linting is specific to the chart versions. A v2 and v3 chart will lint differently. To accomplish this, packages like engine need to be able to handle different chart versions. This was accomplished by some changes: 1. The introduction of a Charter interface for charts 2. The ChartAccessor which is able to accept a chart and then provide access to its data via an interface. There is an interface, factory, and implementation for each version of chart. 3. Common packages were moved to a common and util packages. Due to some package loops, there are 2 packages which may get some consolidation in the future. The new interfaces provide the foundation to move the actions and cmd packages to be able to handle multiple apiVersions of charts. Signed-off-by: Matt Farina <matt.farina@suse.com>	5 months ago
Yuriy Losev	46b1a41631	Add release labels to the release Metadata ... Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>	7 months ago
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>	11 months ago