v0.61.1

🚀 Enhancements

Fix: Duplicate name in portMapping fixed & Docs Updated @Hackerbone (#171)

what

The portMapping parameter had a duplicate name field occurrence

why

Failure in creating services in the new release v0.61.0

references

I was waiting for the previous PR to get merged since I use this module in my project for a while. Saw CI checks didn't pass so I made a new fix PR.

• closes #170

v0.61.0

chore: add service connect fields to portMapping @dudymas (#168)

what

• added name and appProtocol to portMapping variables

why

• Service Connect uses these fields

references

• Service
  Connect

v0.60.1

fix: add port mapping name (#162) @aaronlake (#166)

what

• Add optional variable name to portMappings to allow Service Discovery registration

why

• Unable to allow ECS container definitions to register with Service Discovery

references

• closes #162

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#167)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.60.0

fix: strengthen types, simplify logic (#154) @goruha (#164)

what

• enable & use optional attributes where AWS API marks fields optional
• remove redundant lookups
• strengthen types for log_configuration, repository_credentials, system_controls, container_definition
• reorder object var attributes to match AWS docs
• simplify log configuration sanitization/munging
• simplify secret & environment var sorting
• expose unencoded container definition output directly without requiring pointless jsonencode/jsondecode cycle

why

• optional obviates lookup(..., null) calls for objects
• lookup(o, k) without a default is deprecated in favor of o[k] or direct attr access (o.k)
• log_configuration, repository_credentials, and system_controls had needlessly opaque any types which hinder DX and make subtle bugs more likely (e.g. in the types of log_configuration.options values)
• since all attributes of container_definition are now typed there's no reason not to type it as well
• following the AWS documentation's field order makes types easier to verify for completeness & correctness
• typing log_configuration appropriately obviates explicit tostring & null handling; resolves #151
• env/secret map sorting can be dramatically simplified since for-expressions iterate over maps & objects by key in lexicographic order
• jsonencode-ing the final container definition only to jsondecode for json_map_object is redundant

Refs

• #154
• @obataku

Sync github @max-lobur (#161)

Sync github from the template

v0.59.0

• No changes

v0.58.3

🚀 Enhancements

fix: eternal churn of environment variables @kevcube (#159)

what

• Maybe the AWS container definition API changed but applying a container constructed from this module will post with environment = null which amazon translates to environment = []
• So every subsequent apply will have changes in terraform like environment = [] ~> null

why

• if we match what amazon translates to, then the terraform state stays consistent

v0.58.2

Remove unused provider @pguinard-public-com (#157)

what

• Remove unused provider

why

• Do not download the provider for local.file and local.sensitive_file as this is not required for the module to run
• This makes terraform init run faster as well as download resources that are not used

references

• Local provider that is being defined (#156)
• closes #156

git.io->cloudposse.tools update @dylanbannon (#152)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#155)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.58.1

🚀 Enhancements

Add quick usage using correct source @nitrocode (#141)

what

• Add quick usage using correct source

why

• It's difficult to figure out how to source the module correctly without having to look back at the terraform registry. You could look at the examples too but those source arguments use relative paths instead of the registry source.

references

• N/A

v0.58.0

Resolve issue with mount_points.readOnly bool and TF15 @darpham (#137)

what

• Add backwards compatibility with TF15 related to mount_points variable

why

• Incompatibility with TF15, root cause is unknown

references

• closes #136

comments/notes

• This will force users to specify the readOnly bool, previously where null was specified should now be false per AWS default
• Initially wanted to use default optional function within the variable, but this feature is only available in TF15

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