Marshall Margenau 6546139155 Implement `protected` parameter ... The `protected` parameter will be used to signify that we should never purge a release in FAILED status. You can specify the `continue_processing` param to either skip the failed release and continue on, or to halt armada execution immediately. - Add protected param to Chart schema and documentation. - Implement protection logic. - Moved purging of FAILED releases out of pre-flight and into sync for finer control over protected params. This means failed releases are now purged one at a time instead of all up front. - Added purge and protected charts to final client `msg` return. - Fix: Added missing dry-run protection in tiller delete resources. Change-Id: Ia893a486d22cc1022b542ab7c22f58af12025523		2018-06-17 20:04:53 -05:00
..
__init__.py	feat(api): policy enforcement and api standard	2017-09-20 21:54:39 +00:00
armada.py	Implement `protected` parameter	2018-06-17 20:04:53 -05:00
chartbuilder.py	Fix up Chartbuilder docstrings	2018-04-16 19:16:45 -04:00
document.py	refactor(keystone): reduce keystoneauth usage complexity	2018-06-02 18:20:30 +00:00
k8s.py	Log on k8s watch if no events occur	2018-05-31 16:53:28 -05:00
manifest.py	Fix improper indexing throughout armada handlers	2018-04-17 17:43:47 -04:00
override.py	Fix improper indexing throughout armada handlers	2018-04-17 17:43:47 -04:00
tiller.py	Implement `protected` parameter	2018-06-17 20:04:53 -05:00