armada/armada/cli
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 bugfix(cli): Remove redundant oslo_log register_options calls 2018-06-01 12:11:38 -05:00
apply.py Implement `protected` parameter 2018-06-17 20:04:53 -05:00
delete.py Fix release name bug 2018-06-15 11:21:38 -05:00
rollback.py Expose helm's upgrade/rollback force and recreate pods flags 2018-06-13 11:28:20 -05:00
test.py Fix release name bug 2018-06-15 11:21:38 -05:00
tiller.py feat(validation) Validation messaging 2018-03-15 21:19:43 -04:00
validate.py feat(validation) Validation messaging 2018-03-15 21:19:43 -04:00