Releases: voyagegroup/tf_aws_ecs
Releases · voyagegroup/tf_aws_ecs
v0.6.0
v0.5.0
NEW FEATURES:
- service_load_balancing: support aws fargate #15
- case of specifying var.launch_type = "FARGATE" (currently ver, default as "EC2")
BC BREAKS:
- service_load_balancing: migrate from
placement_strategy
toordered_placement_strategy
#16- it has force renew if apply to existing aws_ecs_service
- if you want update wiwthout destroy, prepare edit to .tfstate
s/placement_strategy/ordered_placement_strategy/g
v0.4.0
BUG FIXES:
- cluster: fix creating only one autoscaling policy when specified multiple thresholds #14
- service_load_balancing: fix creating only one autoscaling policy when specified multiple thresholds #14
BC BREAKS:
Into this module, like rename resource via above changes
(If you do not care about the resource name of this module, or it is not BC BREAKS)
cluster:
-
split resource: (removed module.xxx.aws_autoscaling_policy.scale_in)
- module.xxx.aws_autoscaling_policy.cpu_reservation_low
- module.xxx.aws_autoscaling_policy.cpu_util_low
- module.xxx.aws_autoscaling_policy.memory_reservation_low
- module.xxx.aws_autoscaling_policy.memory_util_low
-
split resource: (removed module.xxx.aws_autoscaling_policy.scale_out)
- module.xxx.aws_autoscaling_policy.cpu_reservation_high
- module.xxx.aws_autoscaling_policy.cpu_util_high
- module.xxx.aws_autoscaling_policy.memory_reservation_high
- module.xxx.aws_autoscaling_policy.memory_util_high
service_load_balancing:
-
split resource: (removed module.xxx.aws_appautoscaling_policy.scale_in)
- module.xxx.aws_appautoscaling_policy.cpu_low
- module.xxx.aws_appautoscaling_policy.memory_low
-
spolit resource: (removed module.xxx.aws_appautoscaling_policy.scale_out)
- module.xxx.aws_appautoscaling_policy.cpu_high
- module.xxx.aws_appautoscaling_policy.memory_high
v0.3.3
v0.3.2
v0.3.1
v0.3.0
BC BREAKS: cluster & service_load_balancing module: variable autoscale_thresholds
splits
to scale_out_thresholds
/ scale_in_thresholds
Code migrations example:
- cluster:
# Before:
module "ex_ecs_cluster" {
source = "[email protected]:voyagegroup/tf_aws_ecs?ref=v0.2.2//cluster"
# ...
autoscale_thresholds = {
cpu_reservation_high = 70
cpu_reservation_low = 10
memory_reservation_high = 80
memory_reservation_low = 20
}
}
# After:
module "ex_ecs_cluster" {
source = "[email protected]:voyagegroup/tf_aws_ecs?ref=v0.3.0//cluster"
# ...
scale_out_thresholds = {
cpu_util = 70
cpu_reservation = 70
memory_util = 80
memory_reservation = 80
}
scale_in_thresholds = {
cpu_util = 70
cpu_reservation = 10
memory_util = 20
memory_reservation = 20
}
}
- service_load_balancing:
# Before:
module "ex_ecs_service" {
source = "[email protected]:voyagegroup/tf_aws_ecs?ref=v0.2.2//service_load_balancing"
# ...
autoscale_thresholds = {
cpu_high = 60
cpu_low = 8
memory_high = 75
memory_low = 10
}
}
# After:
module "ex_ecs_service" {
source = "[email protected]:voyagegroup/tf_aws_ecs?ref=v0.3.0//service_load_balancing"
# ...
scale_out_thresholds = {
cpu = 60
memory = 75
}
scale_in_thresholds = {
cpu = 8
memory = 10
}
}
- cluster: Parameterized to evaluation_periods
scale_out_evaluation_periods
(default: 1)scale_in_evaluation_periods
(default: 2)
- service_load_balancing: Parameterized to evaluation_periods
scale_out_evaluation_periods
(default: 1)scale_in_evaluation_periods
(default: 2)
v0.2.2
v0.2.1
v0.2.0
- BC BREAKS: service_load_balancing: #11 No creating aws_iam_role for application autoscaling
- new variable
autoscale_iam_role_arn
that should specify if enabled autoscaling - related: https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html
- new variable