Releases: cloudposse/terraform-aws-ecs-alb-service-task
Releases · cloudposse/terraform-aws-ecs-alb-service-task
v0.43.0
Update null-label to restore attribute order @Nuru (#87)
what
- Update
terraform-null-labelto restore attribute order handling in place prior to #82
why
- Automatic merging of old attributes with new attributes was added to
terraform-null-labelv0.19.0 and incorporated into this module in #82. However, prior toterraform-null-labelv0.22.1, it placed new attributes in front of old attributes, instead of the previous behavior of this module, which was to place new attributes at the end of the attribute list. This causes unnecessary and unwanted changes in resource names.
references
v0.42.3
🤖 Automatic Updates
Update Terraform cloudposse/label/null to v0.22.1 @renovate (#88)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| cloudposse/label/null (source) | terraform | patch | 0.22.0 -> 0.22.1 |
Release Notes
cloudposse/terraform-null-label
v0.22.1
Add var.attributes to end of context.attributes, not vice versa @Nuru (#114)
what
- Add
var.attributesto end ofcontext.attributes, not vice versa - Update to current workflows (with some exceptions)
why
- Modules should append to attributes passed in, not insert themselves ahead of others
- New features, like auto-format (but holding back some, because this is a special module)
references
- closes #113
- closes #108
v0.42.2
🚀 Enhancements
Add task_exec and task role policy attachments @sodre (#84)
what
- Creates two variables to accept a list of policies to attach to the generated task and task execution roles
- The policies are only attached if the the roles were created by this module.
why
- When creating services that reference outside secrets it would be easier to pass the required policy during service creation.
references
v0.42.1
v0.42.0
Don't pass IAM role to ECS Service when there are more than one Target Groups @msmagoo87 (#83)
what
- In the case of registering more than one Target Group, don't create or pass the ECS service IAM role to the
aws_ecs_serviceblock.
why
- If you are registering multiple target groups to the service, you must allow ECS to create a service-linked role rather than passing one that was manually created. Passing one results in an API error from ECS:
Error: InvalidParameterException: You cannot specify an IAM role for services that require a service linked role.
references
0.41.0: Use context.tf and latest null-label module (#82)
Co-authored-by: actions-bot <[email protected]>
0.40.2
0.40.1: Lookup authorization_config under efs_volume_config (#76)
It was looking for authorization_config under volume instead of efs_configuration Close #74
0.40.0: Make adding all egress rule to the ECS security group optional (#75)
* Make adding all egress rule to the ECS security group optional * Updated README.md Co-authored-by: Alex Taylor <[email protected]> Co-authored-by: actions-bot <[email protected]>
