We had a scenario where beanstalk created a new auto scaling group, the smoke test ran against the old inactive ec2 instance and then eb_deployer swapped the CNAME before the new ec2 instance had started. The result was a period of downtime. Looking at the code the smoke test is run after the environment is updated but before the environment is healthy. Does is make sense to run the smoke test after the environment is healthy?
Hello,
We had a scenario where beanstalk created a new auto scaling group, the smoke test ran against the old inactive ec2 instance and then eb_deployer swapped the CNAME before the new ec2 instance had started. The result was a period of downtime. Looking at the code the smoke test is run after the environment is updated but before the environment is healthy. Does is make sense to run the smoke test after the environment is healthy?
https://github.com/ThoughtWorksStudios/eb_deployer/blob/master/lib/eb_deployer/eb_environment.rb#L32