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

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)

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

what

• Add volumes_from and links

why

• per ContainerDefinition -> VolumesFrom and ContainerDefinition -> Links

what

• Fix the value of second_container_json in the example

why

• Typo

what

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

why

• Support private repositories
• Closes #19

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

what

• Add dnsServers entry to container definition

why

• Missing

what

• Add support for secrets field

why

• ECS task definitions now support a secrets field

what

• Fix example
• Update README

why

• Typo in example
• Added examples to README and fixed typos

what

Add the ability to map multiple ports.

why

Mapping multiple ports was not possible today.

Other things to note:

1. This is a breaking change, as it does away with the individual "container_port", "host_port", and "protocol" configuration in favor of providing the entire "port_mappings" list of maps.
2. This PR changes how environment variables get processed. They are now processed separately and replaced as the last step of output processing. This was done because the current solution was turning the ports into strings, which is invalid configuration for ECS. This effectively rolls back #9 and implements that solution in a new way that is compatible with the port mappings.

what

• Regenerate README.md

why

• Previous version of build-harness has some typos

what

• Add README.yaml

why

• Standardize README