armada/armada
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
..
api Fix release name bug 2018-06-15 11:21:38 -05:00
cli Implement `protected` parameter 2018-06-17 20:04:53 -05:00
common Fix to pass a manifest file to the armada server 2018-06-12 00:53:03 -07:00
conf Remove duplicate option certfile from Armada config 2018-06-13 19:35:25 +01:00
exceptions Implement `protected` parameter 2018-06-17 20:04:53 -05:00
handlers Implement `protected` parameter 2018-06-17 20:04:53 -05:00
schemas Implement `protected` parameter 2018-06-17 20:04:53 -05:00
tests Implement `protected` parameter 2018-06-17 20:04:53 -05:00
utils Fix release name bug 2018-06-15 11:21:38 -05:00
__init__.py fix(init): remove duplicated version code 2018-05-28 05:52:58 -05:00
const.py Revise wait timeouts plus dry-run. 2018-05-30 16:19:35 -05:00
errors.py feat(logging): Enhance logging and update grpcio 2018-03-09 11:36:57 -05:00
shell.py Add command to rollback release to CLI and API 2018-06-06 09:40:31 -05:00
version.py Fix(linting): Make Armada pep8 compliant 2017-09-29 11:46:58 -04:00