In order to limit dropped requests, it would be great if there was a feature that would remove the instance from ELB before restart of apache/ngynx/passenger. Since cap 3 allows deployment to happen on each instance with a wait in the middle, it would be great if this plugin allowed users to take an instance out of elb, deploy the code and then add it back to the ELB before moving on to the next instance.
I am not sure if that is outside of scope of this project but was just wondering what your thoughts are.
In order to limit dropped requests, it would be great if there was a feature that would remove the instance from ELB before restart of apache/ngynx/passenger. Since cap 3 allows deployment to happen on each instance with a wait in the middle, it would be great if this plugin allowed users to take an instance out of elb, deploy the code and then add it back to the ELB before moving on to the next instance.
I am not sure if that is outside of scope of this project but was just wondering what your thoughts are.