Releases: cloudposse/terraform-aws-ecs-container-definition
Releases · cloudposse/terraform-aws-ecs-container-definition
0.43.0: Additional keys
feat: Added missing keys for container definition (#94) * add missed options * update examples * update README * Update examples/complete/versions.tf Co-authored-by: Erik Osterman <[email protected]>
0.42.0 0.12 supports null comparison
what
- remove the
null_value
code
why
- Terraform 0.12 supports conditional operations with null value
references
0.41.0: var.log_configuration type to any
Update variables.tf (#93)
0.40.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#92)
## 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.39.0: Adjustments for variables related to environment (#90)
## what * adjust description for variables related to environment * simplify because of default `environment` value ## why * improve documentation * simplify
0.38.0: Rename JSON Outputs (#89)
* Update outputs.tf * Update examples_complete_test.go * Updated README.md * Update outputs.tf * Update main.tf * Update main.tf * Executed 'terraform fmt' * Update outputs.tf Co-authored-by: actions-bot <[email protected]>
0.37.0: Set user to null to use default in Docker
what
- ECS default behavior is to have this left unset.
- This allows the container to run with the build-specificed
USER
in the Dockerfile (if set, root by default)
why
- The default behavior is to use the container's
USER
runtime. - Defaulting the runtime is a security gap as it can cause containers that were built to run as other users to suddenly start running as root when deployed with this module.
Note, this could break existing container environments running in the wild if they were inadvertently taking advantage of the root access.
0.36.0: Add support for `map_environment` variable
0.35.0: Make secretOptions optional
what
- Make secretOptions optional so the same technique for
mount_points
is used forlog_configuration
why
- Currently the
log_configuration
has to be set tonull
otherwise upon an apply, you will see