0.39.0

[AUTOMATED] Update terraform-null-label versions to support Terraform…

0.38.0: Adds a better container_definition_json description

what

Description of container_definition_json is somewhat obscure regarding the possibility to use multiple container definitions. This MR addresses #69 by making this ability more explicit.

references

• Closes #69

0.37.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#72)

## What

1. Update Version Pinning for Terraform to support 0.13

## Why

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

0.36.0: Adding target group permissions needed for ALB support (#71)

what

• Allow ECS services to register and deregister targets on a Target Group

why

• To support the use of ALBs

references

• #65

0.35.0: Bump label to 0.16.0; allow `environment` to be set (#61)

** what

bump the label module to the latest and allow the environment to be set; add $self to contributors.

0.34.0: Added EFS volume config to ECR fargate task definition (#64)

what

• Recently AWS announced support for EFS volumes in ECS fargate. This pull request adds those options to the task defenition.

why

• To reflect the current ecr task definition volume configuration options

references

• ecs_task_definition.html#efs-volume-configuration-arguments
• Amazon ECS and AWS Fargate support for Amazon EFS File Systems now generally available

0.33.0

Change-Id: Ib507b196870340011e8afdfc1f381ae735ba9099

what

• The previous PR (#63) was incomplete and gives the following error:

Error: "name" must match [\w+=,.@-]

  on .terraform/modules/ecs_alb_service_task/terraform-aws-ecs-alb-service-task-0.32.0/main.tf line 195, in resource "aws_iam_role_policy" "ecs_exec":
 195: resource "aws_iam_role_policy" "ecs_exec" {

• The fix ensures that aws_iam_role_policy and aws_iam_policy_document are not created if task_exec_role_arn is passed in.

why

• Fix the bug.

0.32.0: Task exec role arn (#63)

* task_exec_role_arn: Allow override of task execution role

Change-Id: I69b13345533c5d9ae0eefac9c78a88638e5ee93f

* task_exec_role_arn: Change variable description

Change-Id: Ie320d967b170b31e34af88c5210fd2c85659e9dd

* Updated README.md

Co-authored-by: Andy Hibbert <[email protected]>
Co-authored-by: actions-bot <[email protected]>

0.31.0: Updates to add tags to task_definition

what

Add tags to aws_ecs_task_definition

why

Tags were defined but missing from the task

references

N/A

0.30.0: Override task role

what

Overriding the task role arm instead of the module creating a new task role

why

• When moving an ecs service and task over to this module, there may already be a task role present. If there is already a task role present, we shouldn't have to create a new one, then use the outputs to grab the arn, and attach policies to it. It should be able to reuse an existing role.
• An import of the existing role as the new role also wouldn't work due to the name change which will cause a removal and recreation

references

#58