mirror of
https://github.com/ansible-collections/kubernetes.core.git
synced 2026-11-22 15:10:22 +00:00
fix(helm): validate reuse_values against reset_values and replace (#1230)
* fix(helm): validate reuse_values against reset_values and replace reset_values defaults to true and helm ignores --reuse-values whenever --reset-values is passed, so the documented reuse_values example was a no-op. Warn rather than flip the default, which would silently change what existing playbooks deploy. helm install accepts neither --reuse-values nor --reset-then-reuse-values, so pairing either with replace could only ever make helm report an unknown flag. Fail up front instead, and keep both flags inside the upgrade branch. Fixes #1229 * fix(docstring): neither nor replacing Co-authored-by: Don Naro <dnaro@redhat.com> * fix(helm): warn instead of failing on replace + reuse_values reuse_values has been accepted since 3.0.0, and a converged release never reaches deploy(), so these combinations pass in playbooks today. Failing in main() would turn them red on upgrade. The flags are already dropped from the install path, so warning leaves a valid command behind. Splits the changelog fragment per user-visible change, and covers the helm diff path, whose 'not replace' guards the hard failure had made unreachable. Changes based on the @abikouo's feedback --------- Co-authored-by: Don Naro <dnaro@redhat.com>
This commit is contained in:
co-authored by
Don Naro
parent
094240ab77
commit
10584acdbb
@@ -0,0 +1,6 @@
|
||||
---
|
||||
bugfixes:
|
||||
- helm - fix the ``reuse_values`` example, which set only ``reuse_values=true``. ``reset_values`` defaults to ``true`` and helm ignores ``--reuse-values`` whenever ``--reset-values`` is passed, so following the example reset the release values instead of reusing them (https://github.com/ansible-collections/kubernetes.core/pull/1230).
|
||||
- helm - do not pass the upgrade-only ``--reuse-values`` and ``--reset-then-reuse-values`` flags to ``helm install``, which rejected them with ``unknown flag`` whenever ``reuse_values`` or ``reset_then_reuse_values`` was combined with ``replace`` (https://github.com/ansible-collections/kubernetes.core/pull/1230).
|
||||
minor_changes:
|
||||
- helm - warn when ``reuse_values`` or ``reset_then_reuse_values`` is requested in a combination helm ignores, which happens by default because ``reset_values`` defaults to ``true``, and whenever either is combined with ``replace``. The option descriptions and the examples now state that ``reset_values`` has to be set to ``false`` for either option to take effect (https://github.com/ansible-collections/kubernetes.core/pull/1230).
|
||||
Reference in New Issue
Block a user