11 Commits (e328d00a2ffea7e5e57c2b262087398f85c531fb)

Author	SHA1	Message	Date
Michelle Noorali	2d82b88282	Merge pull request #4364 from michelleN/fix-4337 ... fix(release_server): fix how we merge values	6 years ago
Michelle Noorali	3e0de0dae9	fix(release_server): fix how we merge values ... resolves #4337 Merging maps inside of strings gets a bit tricky. When two strings consisting of "{}" were being added together, this resulted in "{}\n{}" instead of "{}" which is what we wanted. This led to YAML parsing errors and showed up when the `--reuse-values` flag was used when no overrides via `--set` were provided during install and/or upgrade.	6 years ago
Matthew Fisher	2d77db11fa	change copyright to "Copyright The Helm Authors"	7 years ago
Arash Deshmeh	a32868e48b	added ability to handle custom release descriptions to tiller ... Signed-off-by: Arash Deshmeh <adeshmeh@ca.ibm.com>	7 years ago
Michelle Noorali	e02802ba95	ref(pkg/tiller): clarify reuseValues comment	7 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.	7 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.	7 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	7 years ago
Maxim Ivanov	ff5acc9bd8	Make Memory driver to store copy of releases to stop hiding storage errors during tests	7 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	8 years ago