Terraform Aws Ecs Container Definition Versions Save

what

• Cleaner multiple definition example using json_map

why

• Best practices and readability

references

N/A

what

• Small fix in PR https://github.com/cloudposse/terraform-aws-ecs-container-definition/pull/129

why

• See previous PR https://github.com/cloudposse/terraform-aws-ecs-container-definition/pull/129

references

N/A

what

• Adds a null check for secrets and environment

why

• For backwards compatibility https://github.com/cloudposse/terraform-aws-ecs-web-app/pull/134#issuecomment-801882377

references

N/A

what

• Add additional outputs which are marked sensitive which can be used when passing on secrets (secrets) or secret maps (map_secrets).

why

• When using secrets (or map_secrets) and without sensitive outputs TF 0.14 will fail with Error: Output refers to sensitive values

references

• Suggestion to implement it this way was done in https://github.com/cloudposse/terraform-aws-ecs-container-definition/pull/118#issuecomment-785060412

what

• Fixes an issue in a previous PR https://github.com/cloudposse/terraform-aws-ecs-container-definition/pull/123 where value was used instead of valueFrom for the secrets key

why

• This fixes a bug in which the secrets key will break the module due to the incorrect key

references

• Closes https://github.com/cloudposse/terraform-aws-ecs-container-definition/issues/125

Merge copy of https://github.com/cloudposse/terraform-aws-ecs-container-definition/pull/120

Commit history is the same

The original PR was failing on null secrets so I set var.secrets to [] which is the same default as var.environment.

what

Revert sensitive = true outputs

why

Cannot see the difference in task definitions in terraform plan due to sensitive = true

references

Revert https://github.com/cloudposse/terraform-aws-ecs-container-definition/pull/118

what

A key in the container definition had a typo. preudoTerminal instead of pseudoTerminal

why

Because of this typo it was impossible to enable the pseudoTerminal (tty)

references

n/a

what

• Marks the outputs as sensitive
• Update workflows etc. missed by #119

why

• Otherwise TF 0.14 would give an Error: Output refers to sensitive values when using these outputs to feed into other modules (e.g. terraform-aws-ecs-alb-service-task)
• Keep modules in sync per request of Cloud Posse

references

• https://www.terraform.io/upgrade-guides/0-14.html#sensitive-values-in-plan-output

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant