Sean Eagan 2310ddbc2c Remediate releases stuck in non-DEPLOYED statuses ... Armada remediates releases stuck in FAILED status, if not protected, by purging and re-installing them. This implements the same for other non-DEPLOYED statuses. For these statuses it guards this with a best effort determination of whether a previous deployment of the release, either through armada or the helm CLI, is likely still pending based on whether it was last deployed within the chart's wait timeout. If it is deemed likely pending an error is raised, however this condition will eventually expire on future runs allowing for eventual remediation. Reasons why a release may get stuck in statuses other than DEPLOYED or FAILED include: 1. tiller crashed mid-deployment 2. tiller could not reach kubernetes to update the release state 3. running `helm delete <rel>` (without --purge) (DELETED status) Change-Id: Ia89cd59f056103dde47980a149c07a2984c4bbb4		2019-01-18 23:06:01 +00:00
..
__init__.py	[feature] restructure-clean-up-project	2017-06-12 09:06:17 -05:00
keystone.py	Add missing Keystone options to registration of config	2018-06-13 13:18:04 +00:00
release.py	Remediate releases stuck in non-DEPLOYED statuses	2019-01-18 23:06:01 +00:00
source.py	Add caching and cleanup of chart tarballs	2018-10-29 16:02:44 -05:00
validate.py	Fix for get manifest	2018-09-14 15:27:03 +00:00
validation_message.py	Fix: various documentation and URL fixes	2018-09-24 12:53:27 +02:00