Closed bryantbiggs closed 3 years ago
@antonbabenko / @terraform-aws-modules/triage-supporters if you all get some time or have some feedback
ok should be all set @antonbabenko
As the last thing for this massive upgrade, can you write an upgrade guide (similar to this one from ALB module)? Maybe include some rough terraform state mv
commands and a list of renamed variables and outputs. I am pretty sure users will appreciate such information in one place.
@antonbabenko added something in https://github.com/terraform-aws-modules/terraform-aws-autoscaling/pull/139/commits/301ef7c6ef1d2588671c0082facc4f76c3dac43a - let me know what you think
@antonbabenko I think we should be all set. I'll watch for any issues that pop up and address as quickly as I can. we can always update the upgrade doc as well if any feedback comes in 👍🏼
I'm currently using a forked version of this update in production and it works perfectly. I'd like to migrate to an official release. What is the timeframe on getting this merged in?
Appreciate all the hard work you guys put into this, for real.
@bansawbanchee It will be released during an hour (running it for the last time as we speak).
We wanted to drop Terraform 0.12 during this major release but this code actually works with 0.12 :) Great job @bryantbiggs !
v4.0.0 has been just released.
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
Motivation and Context
closes #51 closes #54 closes #76 closes #84 closes #86 closes #117 closes #124 closes #126 closes #130 closes #137
Breaking Changes
v4.0.0
)For users that come across this change/release - the recommended approach to updates would be to provision a new autoscaling group alongside your existing before deprecating/removing the existing autoscaling group. if you are using load balancers in front of your autoscaling groups, this is a matter of updating the target groups. autoscaling groups are generally meant to be orchestrating instances that are ephemeral (or that can be replaced) and therefore provisioning a new autoscaling group alongside your existing and switching any load/traffic over to it should suffice for those who wish to upgrade.
How Has This Been Tested?
examples/*
projects