Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Warming up new stack ignores min/desired/max of existing stack #9

Closed
robsweet opened this issue Aug 14, 2014 · 2 comments
Closed

Warming up new stack ignores min/desired/max of existing stack #9

robsweet opened this issue Aug 14, 2014 · 2 comments

Comments

@robsweet
Copy link

If the min/desired/max of a Blue stack have been modified manually, when Green is deployed, it only warms the new stack to the settings in the JSON instead of to what's set on the Blue stack. It should respect the Blue stack's settings and throw a warning.
@ehaynes99 ehaynes99 mentioned this issue Oct 20, 2015
Closed
@robsweet
Copy link
Author

robsweet commented Dec 3, 2015

Why was this closed? Does the new logic from #31 work around it?

@ehaynes99
Copy link

This was actually fixed long ago (diff lost in initial commit to public repo in auto_scaling_group_swap in 1d2f9f2 ).

#31 was a regression caused by it, which is now also fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@robsweet @ehaynes99