elasticbeanstalk: waiter: EnvironmentUpdated = Immediately Fail/Exit on Particular Conditions?

[colinbjohnson]

Based on my understanding we could have the EnvironmentUpdated waiter for ElasticBeanstalk exit and fail on particular cases such as HealthStatus: Degraded or Health: Red.

I think our options are:

• do nothing / keep the current behavior <- this involves the least code and logic
  • this behavior would likely be frustrating for users who wait 400 seconds and then find out an environment update had failed (had they known this they might have investigated)
  • we might want to add some information in the aws: elasticbeanstalk: wait: environment-updated document or suggest that for some instances using the eb cli and deploy command would be a better option
• add acceptors (https://github.com/boto/botocore/blob/develop/botocore/data/elasticbeanstalk/2010-12-01/waiters-2.json) that catch failures
• do something else?