armada/armada
Mark Burnett df91412ed6 Works around low RELEASE_LIMIT by increasing it
We have been deploying in the low 60's of charts in many environments,
but the current treasuremap environment is running 68.

This led to a situation where tiller would find all 68 charts, but then
return only the newest 64 (RELEASE_LIMIT) in its response.  That meant
that armada did not see those charts when deciding whether to install or
upgrade.

Change-Id: I5d2a06f806006947ad48cc0e24b3f91baa3f37fd
2018-04-17 14:39:05 -05:00
..
api style(pep8): remove unreferenced variables 2018-04-15 16:01:22 -05:00
cli bug(deleted jobs) Armada deleting jobs during upgrade 2018-04-13 00:30:21 -04:00
common feat(logging): Enhance logging and update grpcio 2018-03-09 11:36:57 -05:00
conf Updated Makefile 2018-03-15 12:40:19 -04:00
exceptions Fix chartbuilder get_files raising UnicodeDecodeError 2018-03-22 17:13:58 -05:00
handlers Works around low RELEASE_LIMIT by increasing it 2018-04-17 14:39:05 -05:00
schemas feat(validation) Validation messaging 2018-03-15 21:19:43 -04:00
tests Fix Armada raising 500 following unsupported media type 2018-03-29 22:11:53 -04:00
utils feat(validation) Validation messaging 2018-03-15 21:19:43 -04:00
__init__.py Fix(linting): Make Armada pep8 compliant 2017-09-29 11:46:58 -04:00
const.py bug(tests): Unskip Armada API unit tests 2017-12-14 17:02:50 -04:00
errors.py feat(logging): Enhance logging and update grpcio 2018-03-09 11:36:57 -05:00
shell.py style(armada): quality of life and cleanup 2018-02-12 10:27:11 -05:00
version.py Fix(linting): Make Armada pep8 compliant 2017-09-29 11:46:58 -04:00