armada/armada
Sean Eagan 3807db1b6e Fail wait when no resources found
This removees a fail-safe that allowed releases which did not
contain pods (intentionally) to still succeed after a best effort
to wait for them until timeout.

Now that we have the ability to disable waiting on resource types
`wait.resources` [0], this fail-safe is no longer needed.

Now when resources are not found, armada will fail with a message
for the user to check their `wait.resources` and labels and
configure as needed. This way we can prompt the user to remove
unnecessary waiting from their deployments.

There is also a longer term plan to make these configurations less
often needed [1].

[0]: https://review.openstack.org/#/c/603901/
[1]: https://review.openstack.org/#/c/636440/

Change-Id: I859326470ecba49f2301705409c51312a601e653
2019-03-01 17:41:50 -06:00
..
api Don't log health checks 2019-02-27 09:27:38 -06:00
cli Merge "Add support in Armada CLI to pass user bearer tokens to tiller" 2019-02-28 14:47:02 +00:00
common Fix Flake8 3.6.0 errors 2018-10-26 09:23:42 -04:00
conf Parallelize unsequenced chart group deployments 2018-10-03 10:27:49 -05:00
exceptions Remediate releases stuck in non-DEPLOYED statuses 2019-01-18 23:06:01 +00:00
handlers Fail wait when no resources found 2019-03-01 17:41:50 -06:00
schemas test: Add test-specific timeout option 2019-02-20 17:03:01 -06:00
tests test: Add test-specific timeout option 2019-02-20 17:03:01 -06:00
utils Don't log unsupported document type messages 2019-02-28 15:57:18 -06:00
__init__.py fix(init): remove duplicated version code 2018-05-28 05:52:58 -05:00
const.py test: Add test-specific timeout option 2019-02-20 17:03:01 -06:00
shell.py Adding yapf config, plus formatted code. 2018-06-22 14:56:04 -05:00
version.py Fix(linting): Make Armada pep8 compliant 2017-09-29 11:46:58 -04:00