You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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>		2 years ago
..
driver	Merge pull request #8470 from mikeshng/sql-query-fix	3 years ago
storage.go	fix: "... has no deployed releases" error when release history contains only failed releases and history limit reached	2 years ago
storage_test.go	fix: "... has no deployed releases" error when release history contains only failed releases and history limit reached	2 years ago