v0.61.2

feature: Add restart policy and version consistency parameters @ia9 (#193)

## what

• Add restartPolicy parameter
• Add versionConsistency parameter
• Update docs
• Update complete example

why

In order to support new parameters added to container definition.

• restartPolicy parameter
• versionConsistency parameter added in AWS provider v5.77.0

references

• ContainerDefinition
• Implements #192
• Closes #191

🤖 Automatic Updates

Migrate new test account @osterman (#190)

## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

Update .github/settings.yml @osterman (#189)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @osterman (#187)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#186)

## what - Update workflows (`.github/workflows`) to use shared workflows from `.github` repo

why

• Reduce nested levels of reusable workflows

Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#185)

## what - Update workflows (`.github/workflows`) to add `issue: write` permission needed by ReviewDog `tflint` action

why

• The ReviewDog action will comment with line-level suggestions based on linting failures

Update GitHub workflows @osterman (#184)

## what - Update workflows (`.github/workflows/settings.yaml`)

why

• Support new readme generation workflow.
• Generate banners

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#183)

## what

• Install latest GitHub Action Workflows

why

• Use shared workflows from cldouposse/.github repository
• Simplify management of workflows from centralized hub of configuration

Add GitHub Settings @osterman (#182)

## what - Install a repository config (`.github/settings.yaml`)

why

• Programmatically manage GitHub repo settings

Update Scaffolding @osterman (#180)

## what - Reran `make readme` to rebuild `README.md` from `README.yaml` - Migrate to square badges - Add scaffolding for repo settings and Mergify

why

• Upstream template changed in the .github repo
• Work better with repository rulesets
• Modernize look & feel

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