Cristian Klein 9a4f4ec64b fix(helm): Avoid corrupting storage via a lock ... If two `helm upgrade`s are executed at the exact same time, then one of the invocations will fail with "already exists". If one `helm upgrade` is executed and a second one is started while the first is in `pending-upgrade`, then the second invocation will create a new release. Effectively, two helm invocations will simultaneously change the state of Kubernetes resources -- which is scary -- then two releases will be in `deployed` state -- which can cause other issues. This commit fixes the corrupted storage problem, by introducting a poor person's lock. If the last release is in a pending state, then helm will abort. If the last release is in a pending state, due to a previously killed helm, then the user is expected to do `helm rollback`. Closes #7274 Signed-off-by: Cristian Klein <cristian.klein@elastisys.com>		5 years ago
..
hook.go	feat(*): Adds custom time package for better marshalling	5 years ago
info.go	feat(*): Adds custom time package for better marshalling	5 years ago
mock.go	ref(time): Adds wrapper for most time stdlib methods	5 years ago
release.go	Add comments about release Version variable	5 years ago
responses.go	ref(*): remove dead code	6 years ago
status.go	fix(helm): Avoid corrupting storage via a lock	5 years ago