You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
5
5
The format is based on [Keep a Changelog](http://keepachangelog.com/) and this
6
6
project adheres to [Semantic Versioning](http://semver.org/).
7
7
8
+
## [v3.2.0] - 2018-03-28
9
+
10
+
### Changed
11
+
12
+
*`create_before_destroy` lifecycle policy added to the target groups. This allows target groups to be modified, though means they're recreated anytime they're changed. A change MUST include a change to the `name` value or will fail on duplicates. (nice work, @egarbi 🦄)
It's strongly recommended that the autoscaling module is instantiated in the same
29
+
state as the ALB module as in flight changes to active target groups need to be propagated
30
+
to the ASG immediately or will result in failure. The value of `target_group[n][name]` also must change any time there are modifications to existing `target_groups`.
31
+
26
32
## Why ALB instead of ELB
27
33
28
34
The use-case presented here appears almost identical to how one would use an ELB
@@ -43,17 +49,17 @@ A full example leveraging other community modules is contained in the [examples/
0 commit comments