9 commits

Author	SHA1	Message	Date
Timofey Kirillov	7f68bfa1fa	fix: added resource info into the validation error ... Signed-off-by: Timofey Kirillov <timofey.kirillov@flant.com>	2021-11-12 19:00:43 +03:00
Matt Farina	b7c38c879a	Adding support for k8s 1.19 ... Closes #8806 Signed-off-by: Matt Farina <matt@mattfarina.com>	2020-09-25 12:15:06 -04:00
Jacob LeGrone	8d1de39fe3	Add more detail to error messages and support a non-force mode in metadata visitor ... Signed-off-by: Jacob LeGrone <git@jacob.work>	2020-03-10 22:22:15 -04:00
Jacob LeGrone	271cb2268b	Alternative: annotation-only solution ... Signed-off-by: Jacob LeGrone <git@jacob.work>	2020-02-20 21:11:52 -05:00
Jacob LeGrone	a29365b3c6	Adopt resources into release with correct instance and managed-by labels ... Signed-off-by: Jacob LeGrone <git@jacob.work>	2020-02-20 20:21:33 -05:00
bakito	ab905010fd	fix error output ... Signed-off-by: Marc Brugger <github@bakito.ch>	2020-01-08 18:46:10 +01:00
Marc Brugger	8231b17c31	print gvk information on existing resource conflict ... Signed-off-by: Marc Brugger <github@bakito.ch>	2019-11-07 16:30:01 +01:00
Matt Farina	9bc7934f35	Updating the module for v3 as the major version ... Signed-off-by: Matt Farina <matt@mattfarina.com>	2019-10-03 14:27:05 -04:00
Taylor Thomas	36f3a4b326	fix(action): Protects against current resource conflicts ... Currently, if using the --atomic flag or deleting a release that failed due to an already existing resource, Helm will deleting those resources that aren't managed by it. This PR fixes the issue by checking for pre-existing resources during install and upgrade. This is done as a validation step so the release will not even be started if resources currently exist. This PR is inspired by @xchapter7x's work in #3477. This also fixes a small bug in upgrade where deletes fail if the resource was already deletes Fixes #6407 Signed-off-by: Taylor Thomas <taylor.thomas@microsoft.com>	2019-09-30 16:11:40 -06:00