0.13.0 Add support for `dependsOn` parameter

what

• Add support for dependsOn parameter

why

• New parameter supported by AWS

references

• https://docs.aws.amazon.com/AmazonECS/latest/developerguide/example_task_definitions.html#example_task_definition-containerdependency

0.12.0 Add user, fix negative numbers

what

• Add user parameter
• Fix negative numbers

why

• Add user variable - the user to run as inside the container
• Fix the conversion of quoted negative numbers ("-1") to numbers (-1)

0.11.0 Support optional container_cpu, container_memory and container_memory_reservation

what

• Support optional container_cpu, container_memory and container_memory_reservation

why

• These 3 fields could be optional when using Fargate type.
  However, the current module does not allow the caller to remove these fields from the container definition.
  AWS will fail the definition if we set to 0 directly. We replace 0 to null for these 3 fields so terraform apply could work

0.10.0 Add volumes_from and links

what

• Add volumes_from and links

why

• per ContainerDefinition -> VolumesFrom and ContainerDefinition -> Links

0.9.1 Fix the value of `second_container_json` in the example

what

• Fix the value of second_container_json in the example

why

• Typo

0.9.0 Support private repositories

what

• Added repository_credentials, a map which corresponds to the repositoryCredentials JSON key

why

• Support private repositories
• Closes #19

0.8.0 Add ulimits to container definition

what

• Add ulimits to container definition

why

• The ulimits set constraints on how many resources a container can consume so that it doesn't deplete all available resources on the host

references

• https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-taskdefinition-containerdefinitions-ulimit.html
• https://docs.amazonaws.cn/en_us/AWSCloudFormation/latest/UserGuide/aws-properties-ecs-taskdefinition-containerdefinitions.html

0.7.0 Add `dnsServers` entry to container definition

what

• Add dnsServers entry to container definition

why

• Missing

0.6.1: Set secrets to null if empty list (#18)

I've seen the following error from Terraform with an empty list of
secrets:

```
* aws_ecs_task_definition.task_definition: ClientException: When you are specifying container secrets, you must also specify a value for 'executionRoleArn'.
        status code: 400, request id: 8e82fc41-1039-11e9-a6c6-d14d7e4d29d9
```

This commit sets secrets to `null` if it's an empty list.

0.6.0 Add support for `secrets` field

what

• Add support for secrets field

why

• ECS task definitions now support a secrets field