Skip to content

Releases: cloudposse/terraform-aws-ecs-container-definition

v0.57.0

11 Jun 16:31
@cloudpossebot cloudpossebot
0.57.0
ec4c4a6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.57.0
Fix: Add Thorough Automated Testing and Bump Minimum Terraform Version to 0.13.0 @korenyoni (#139)

what

  • Ensure examples/complete is creating an aws_ecs_task_definition and test the task definition in the automated testing.
  • Fix examples/multiple_definitions
  • Bump minimum Terraform required version to 0.13.0
  • Add context.tf to examples/complete to ensure aws_ecs_task_definition has tags.

why

  • We should be ensuring that the entire container definition output of this module is accepted by aws_ecs_task_definition and produces an identical result to the resource container_definitions output.
  • Bumping to 0.13.0 as the minimum supported version ensures this module is easier to maintain down the road.

references

  • N/A
Loading

v0.56.0

26 Mar 16:05
@cloudpossebot cloudpossebot
0.56.0
549d7a0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.56.0
Cleaner multiple definition example using json_map @nitrocode (#131)

what

  • Cleaner multiple definition example using json_map

why

  • Best practices and readability

references

N/A

Loading

v0.55.0

18 Mar 22:31
@cloudpossebot cloudpossebot
0.55.0
f7bace8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.55.0
Null checks for secrets and environment @nitrocode (#130)

what

  • Small fix in PR #129

why

  • See previous PR #129

references

N/A

Loading

v0.54.0

18 Mar 22:00
@cloudpossebot cloudpossebot
0.54.0
4b047d8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.54.0
Add checks for var.secrets and var.environment @nitrocode (#129)

what

  • Adds a null check for secrets and environment

why

references

N/A

Loading

v0.53.0

08 Mar 18:08
@cloudpossebot cloudpossebot
0.53.0
41cb05d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.53.0
add sensitive variants of outputs @syphernl (#124)

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

Loading

v0.52.0

02 Mar 20:05
@cloudpossebot cloudpossebot
0.52.0
8be4985
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.52.0
secrets valueFrom @nitrocode (#126)

what

  • Fixes an issue in a previous PR #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

Loading

v0.51.0

26 Feb 19:48
@cloudpossebot cloudpossebot
0.51.0
bb62a1a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.51.0
feat: add map_secrets @davidvasandani (#120) @nitrocode (#123)

Merge copy of #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.

Loading

v0.50.0

23 Feb 17:55
@cloudpossebot cloudpossebot
0.50.0
b982a63
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.50.0
Remove sensitive outputs @nitrocode (#122)

what

Revert sensitive = true outputs

why

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

references

Revert #118

Loading

v0.49.2

09 Feb 04:32
@cloudpossebot cloudpossebot
0.49.2
986d530
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.49.2

🐛 Bug Fixes

Fix typo in key of container definition @clifford-sanders (#121)

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

Loading

v0.49.1

09 Feb 04:27
@cloudpossebot cloudpossebot
0.49.1
b5eff64
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.49.1

🚀 Enhancements

fix: mark outputs as sensitive @syphernl (#118)

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

Loading