14 Commits (2a97768b5c360e11af3e8b88fd05c83d9b24054c)

Author	SHA1	Message	Date
Adam Reese	2a97768b5c	ref(pkg/tiller): flatten package structure for storage	8 years ago
Adam Reese	4c95185164	ref(*): replace chart.config with []byte	8 years ago
Adam Reese	36536d77ba	ref(*): remove protobuf any type	8 years ago
Adam Reese	91a6ebfed5	ref(*): remove protobuf timestamps	8 years ago
Adam Reese	6345f04190	ref(hapi): convert protobuf to go types	8 years ago
Adam Reese	496ca54183	ref(*): bypass grpc for helm client	8 years ago
Adam Reese	62804848c6	ref(pkg/tiller): refactor out imports of pkg/helm	8 years ago
Michelle Noorali	e02802ba95	ref(pkg/tiller): clarify reuseValues comment	8 years ago
Michelle Noorali	9266731dc4	fix(pkg/tiller): reuseValues combines all prev val ... Resolves #3655 We were seeing that when running helm upgrade with the reuse-values flag enabled that you could end up in the position where overrides a.k.a computed values from previous revisions were not being saved on the updated revision. This left us in a weird position where some computed values would disappear mysteriously in the abyss. That happened because computed values from previous revisions weren't merged with the new computed values every time the reuse-values flag was used. This PR merges computed values from the previous revisions so you don't end up in that kind of conundrum.	8 years ago
Matthew Fisher	13730b0dab	replace FAILED deployments with `helm upgrade --install --force` ... When using `helm upgrade --install`, if the first release fails, Helm will respond with an error saying that it cannot upgrade from an unknown state. With this feature, `helm upgrade --install --force` automates the same process as `helm delete && helm install --replace`. It will mark the previous release as DELETED, delete any existing resources inside Kubernetes, then replace it as if it was a fresh install. It will then mark the FAILED release as SUPERSEDED.	8 years ago
Adam Reese	82ef751414	fix(tiller): upgrade last deployed release ... Fixes #2437 Two bugs were causing this behavior - Tiller was marking the previous release superseded when an upgrade failed. - Upgrade was diffing against failed releases	8 years ago
Maxim Ivanov	ff5acc9bd8	Make Memory driver to store copy of releases to stop hiding storage errors during tests	8 years ago
Adam Reese	eccb041c0f	ref(tiller): cleanup goimports	8 years ago
fibonacci1729	22db973932	ref(tiller): refactor tests into logical files ... TestListReleasesByStatus -> tiller/release_list_test.go TestListReleasesFilter -> tiller/release_list_test.go TestListReleasesSort -> tiller/release_list_test.go TestListReleases -> tiller/release_list_test.go TestUpdateRelease_ResetReuseValues -> tiller/release_update_test.go TestUpdateRelease_ResetValues -> tiller/release_update_test.go TestUpdateRelease_ReuseValues -> tiller/release_update_test.go TestUpdateReleaseNoChanges -> tiller/release_update_test.go TestUpdateReleaseFailure -> tiller/release_update_test.go TestUpdateReleaseNoHooks -> tiller/release_update_test.go TestUpdateRelease -> tiller/release_update_test.go TestRollbackReleaesFailure -> tiller/release_rollback_test.go	9 years ago