27 Commits (d70e293e5fea032e843c29d15c7e85e78b0aca6b)

Author	SHA1	Message	Date
Timofey Kirillov	da8e7d2532	fix: "... has no deployed releases" error when release history contains only failed releases and history limit reached ... Fixed old releases rotation procedure to not require a deployed release to exists. An error will arise when there are no successfully deployed release yet, but releases history limit has been reached. In such situation helm will refuse to upgrade release anymore with "... has no deployed releases" error. Furthermore, release rotation procedure already expecting lastDeployedRelease to be either nil, or not nil. So it is assumed that deployed release may exist or may not and these both outcomes were already expected as a valid situation rather than a failure. Reworked storage_test.go TestStorageRemoveLeastRecentWithError test case: use mocked driver and test release creation procedure does not shadows errors from the underneath release rotation procedure. Signed-off-by: Timofey Kirillov <timofey.kirillov@flant.com>	3 years ago
Josh Soref	2bf8fdf45d	chore: Spelling (#9410) ... * spelling: annotate Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: asserts Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: behavior Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: binary Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: contain Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: copied Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: dependency Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: depending Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: deprecated Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: doesn't Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: donot Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: github Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: inputting Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: iteration Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: jabberwocky Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: kubernetes Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: length Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: mismatch Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: multiple Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: nonexistent Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: outputs Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: panicking Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: plugins Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: parsing Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: porthos Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: regular Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: resource Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: repositories Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: something Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: strict Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: string Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: unknown Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>	4 years ago
Daniel Lipovetsky	8c28da6567	test(pkg/storage): Verify that storage.Create returns an error if it fails to clean up least-recent release versions ... Signed-off-by: Daniel Lipovetsky <dlipovetsky@d2iq.com>	4 years ago
Eric Bailey	b9445616b5	fix(storage): preserve last deployed revision (#7806) ... Signed-off-by: Eric Bailey <eric@ericb.me>	5 years ago
Cristian Klein	1f0582cadc	fix(helm): improve handling of corrupted storage ... Helm does not yet properly handle concurrent executions (see #7322), and invoking Helm concurrently on the same release lead to corrupted storage. Specifically, several Releases may be marked as DEPLOYED. This patch improved handling of such situations, by taking the latest DEPLOYED Release. Eventually, the storage will clean itself out, after the corrupted Releases are deleted due to --history-max. This is a port to Helm v3 of #7319. Signed-off-by: Cristian Klein <cristian.klein@elastisys.com>	5 years ago
Matt Farina	9bc7934f35	Updating the module for v3 as the major version ... Signed-off-by: Matt Farina <matt@mattfarina.com>	5 years ago
Adam Reese	895e9192d4	feat(*): use vanity import helm.sh/helm ... Signed-off-by: Adam Reese <adam@reese.io>	6 years ago
Matthew Fisher	2571dbf82f	ref: remove pkg/helm, pkg/hapi, pkg/tiller ... Signed-off-by: Matthew Fisher <matt.fisher@microsoft.com>	6 years ago
Martin Hickey	45fb4b1c44	Fix linter warnings ... Signed-off-by: Martin Hickey <martin.hickey@ie.ibm.com>	6 years ago
Adam Reese	4f26b658d8	change copyright to "Copyright The Helm Authors"	6 years ago
Matthew Fisher	195d21d5d7	ref(cmd): rename `helm delete` to `helm uninstall` ... To match the convention of `helm install`, `helm uninstall` is the inverse. Other tangential changes in this PR: - StatusDeleting has been changed to StatusUninstalling - StatusDeleted has been changed to StatusUninstalled - `helm list --deleted` has been changed to `helm list --uninstalled` - `helm list --deleting` has been changed to `helm list --uninstalling` - `helm.DeleteOption` and all delete options have been renamed to `helm.UninstallOption` I have not made any changes to the "helm.sh/hook-delete-policy", "pre-delete" and "post-delete" hook annotations because 1. it's a major breaking change to existing helm charts, which we've commited to NOT break in Helm 3 2. there is no "helm.sh/hook-install-policy" to pair with "helm.sh/hook-uninstall-policy", so delete still makes sense here `helm delete` and `helm del` have been added as aliases to `helm uninstall`, so `helm delete` and `helm del` still works as is.	7 years ago
Adam Reese	3b9596c6ab	ref(*): convert const types to strings	7 years ago
Adam Reese	c5a76deba3	ref(*): use go conventions for naming types	7 years ago
Adam Reese	6345f04190	ref(hapi): convert protobuf to go types	7 years ago
Matt Butcher	0853f4906a	feat(tiller): limit number of versions stored per release ... This adds a new configuration option to Tiller to limit the number of records stored per release. Tiller stores historical release information (helm history, helm rollback). This makes it possible to set a maximum number of versions per release. To enable this feature, use `helm init --history-max NNN`. Note that because of the restrictions on Deployment objects, you will have to re-install Tiller to add a limit. Along the way, I found an unreported bug in the Memory storage driver. This fixes that bug and adds substantially more tests to catch regressions. Closes #2332	7 years ago
Justin Scott	fa68a6e1db	fix(tiller): remove locking system from storage and rely on backend controls ... Tiller currently hangs indefinitely when deadlocks arise from certain concurrent operations. This commit removes the nested mutex locking system from pkg/Storage and relies on resource contention controls in k8s. Closes #2560	8 years ago
Maciej Kwiek	ec92b76054	Release are locked to avoid parallel changes ... Environment is supplied with release lock map which allows to lock a release by name to make sure that update, rollback or uninstall aren't running on one release at the same time.	8 years ago
Matt Butcher	a5d96c2704	fix(tiller): fix spurious "no release found" errors. ... There are some places where releases are only located if they are in the state DEPLOYED. That particular logic was incorrectly used for upgrades. That caused #1566. While fixing that issue, I found that this was also the root cause of #1587 (though because it was off by one). I added a generic method to get the last release, regardless of its status. This allows some behaviors that previously failed: - 'helm upgrade' can now be performed on a DELETED release - 'helm rollback' can now be performed on a DELETED release even if there is only one revision of that release history. Closes #1566 Closes #1587	8 years ago
fibonacci1729	e9dd302a9c	feat(helm/cmd): support for retrieving release history	8 years ago
fibonacci1729	e25732284b	feat(rollback-storage): gofmt, added missing license headers, and canconical import paths	8 years ago
fibonacci1729	383a9c186a	update pkg/storage to support rollback	8 years ago
fibonacci1729	3dca699410	fix: storage tests	9 years ago
fibonacci1729	a83425d44b	style & doc comments	9 years ago
fibonacci1729	967e438bfd	gofmt ...	9 years ago
fibonacci1729	bfd6712c94	add filtering mechanism to storage and embed Driver directly into Storage	9 years ago
fibonacci1729	aff817a1fc	run gofmt	9 years ago
fibonacci1729	4210d60c5e	add storage type to interface with multiple drivers	9 years ago