6b96bbf28d
This fixes the following issues with listing releases from tiller, which could cause Armada to be confused about the state of the latest release, and do the wrong thing. - Was not filtering out old releases, so we could find both a FAILED and DEPLOYED release for the same chart. When this is the case it likely means the FAILED release is the latest, since otherwise armada would have purged the release (and all its history) upon seeing the FAILED release in a previous run. The issue is that after the purge it would try to upgrade rather than re-install, since it also sees the old DEPLOYED release. Also if a release gets manually fixed (DEPLOYED) outside of armada, armada still sees the old FAILED release, and will purge the fixed release. - Was only fetching DEPLOYED and FAILED releases from tiller, so if the latest release has another status Armada won't see it at all. This changes to: - Fetch releases with all statuses. - Filter out old releases. - Raise an error if latest release has status other than DEPLOYED or FAILED, since it's not clear what other action to take in this scenario. Change-Id: I84712c1486c19d2bba302bf3420df916265ba70c |
||
---|---|---|
.. | ||
api-exceptions.inc | ||
armada-exceptions.inc | ||
base-exceptions.inc | ||
chartbuilder-exceptions.inc | ||
guide-exceptions.rst | ||
index.rst | ||
k8s-exceptions.inc | ||
manifest-exceptions.inc | ||
override-exceptions.inc | ||
source-exceptions.inc | ||
tiller-exceptions.inc | ||
validate-exceptions.inc |