v0.57.0 Unstable Pre-Release

We are revising and standardizing our handling of security groups and security group rules across all our Terraform modules. This is an early attempt with significant breaking changes. We will make further breaking changes soon, so using this version is not recommended.

feat: use security-group module instead of resource @SweetOps (#117)

what

• use security-group module instead of resource
• update tests

why

• more flexible than current implementation
• bring configuration of security group/rules to one standard

references

• CPCO-409

v0.56.0

Add ECS Service with ignore desired_count @realrill (#116)

what

• Add ignore_desired_count aws_ecs_service that has lifecycle setup to ignore desired_count changes

why

• Desired count is a rough estimate that can be volatile during peak hours of the service that the containers serve
• Autoscaling policies may have scaled the number of tasks to above/below the desired count, so on a deployment of a new feature/change we don't want the desired count to be reset

references

• No GitHub Issue for this as far as I'm aware

v0.55.1

🚀 Enhancements

remove unused provider @mikkelam (#114)

what

I removed the template provider

why

It is not used anywhere and the provider itself is deprecated and without a darwin arm64 release, making it unusable for new macbook users.

v0.55.0

enable_execute_command added to be able to use ECS Exec @maximmi (#113)

what

• enable_execute_command added

why

• to be able to use ECS Exec

references

• https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-exec.html

v0.54.2

🚀 Enhancements

feat: add force_new_deployment variable @syphernl (#112)

what

• Added the force_new_deployment flag to force new task deployment of the service
• Updated github configs

why

• To make it possible to force a new deployment

v0.54.1

🚀 Enhancements

Add create_before_destroy lifecycle to sg @nitrocode (#111)

what

• Add name_prefix and lifecycle to sg

why

• Name changes to the security group may not be able to be destroyed easily.

references

• #77

note

Unsure if both the lifecycle and the name_prefix args need to be set. Might be good enough just to do the lifecycle.

I'm thinking it might be better to remove the name_prefix and see if the lifecycle clears the issue for the user.

v0.54.0

Add var.service_role_arn @nitrocode (#110)

what

• Add var.service_role_arn

why

• We reuse our service role and would like to reuse it within this module to save us from creating a redundant role

references

• #81

v0.53.0

Add input variable for ecs service wait_for_steady_state @nitrocode (#109)

what

• Add input variable for ecs service wait_for_steady_state
• Defaults to false which is the default on the aws_ecs_service resource

why

• Allows the module to wait until the service is in a steady state before applying successfully

references

• #91

v0.52.0

Reuse existing task definition family and revision @nitrocode (#108)

what

• Reuse existing task definition family and revision

why

• I'd like to recreate a service on a new cluster without having to recreate the task definition. By supplying the task definition family and revision, I can achieve this.

references

• #80

v0.51.0

Only create the sg if network_mode == awsvpc @nitrocode (#107)

what

• Only create the sg if network_mode == awsvpc

why

• Looks like the security group is used only if var.network_mode = "awsvpc"

references

• #102