7 Commits (bf96db7e8ac266c4c7caca31d4852565c80814a6)

Author	SHA1	Message	Date
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>	5 years ago
Jacob LeGrone	271cb2268b	Alternative: annotation-only solution ... Signed-off-by: Jacob LeGrone <git@jacob.work>	5 years ago
Jacob LeGrone	a29365b3c6	Adopt resources into release with correct instance and managed-by labels ... Signed-off-by: Jacob LeGrone <git@jacob.work>	5 years ago
bakito	ab905010fd	fix error output ... Signed-off-by: Marc Brugger <github@bakito.ch>	5 years ago
Marc Brugger	8231b17c31	print gvk information on existing resource conflict ... Signed-off-by: Marc Brugger <github@bakito.ch>	5 years ago
Matt Farina	9bc7934f35	Updating the module for v3 as the major version ... Signed-off-by: Matt Farina <matt@mattfarina.com>	5 years ago
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>	5 years ago