chore(deps): update terraform cloudposse/ecs-container-definition/aws to v0.55.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ecs-container-definition/aws (source)	terraform	minor	0.49.2 -> 0.53.0

---

Release Notes

cloudposse/terraform-aws-ecs-container-definition

v0.53.0

Compare Source

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 * Suggestion to implement it this way was done in https://github.com/cloudposse/terraform-aws-ecs-container-definition/pull/118#issuecomment-785060412

v0.52.0

Compare Source

secrets valueFrom @​nitrocode (#​126)

#### 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

v0.51.0

Compare Source

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.

v0.50.0

Compare Source

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 https://github.com/cloudposse/terraform-aws-ecs-container-definition/pull/118

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[nitrocode]

/test all

[Nuru]

@nitrocode Looks like this module needs to be updated to work with the changes in cloudposse/ecs-container-definition/aws . I have not looked into the details, but if possible, it would be better to update cloudposse/ecs-container-definition/aws so that it remains backwards compatible.

Example error from test:

Error: Iteration over null value

  on .terraform/modules/ecs_web_app.container_definition/main.tf line 20, in locals:
  20:   secrets_values      = var.map_secrets != null ? values(var.map_secrets) : [for m in local.secrets_vars : lookup(m, "valueFrom")]
    |----------------
    | local.secrets_vars is null

A null value cannot be used as the collection in a 'for' expression.

[nitrocode]

I changed the default of var.secrets changed from null to [] so it would be 1:1 with var.environment in cloudposse/terraform-aws-ecs-container-definition#123. I think it would be better to apply the same consistency in this repo.

Edit: on second thought, might be better to just have better conditional logic in the ecs container definition module.

[nitrocode]

/test all

[nitrocode]

/test all

[nitrocode]

Seems like we have a nat gateway failure which is not relevant to this upgrade.

[nitrocode]

/test terratest

[nitrocode]

/test test/terratest

[cloudposse-mergebot]

We've automatically approved this PR because the checks from the automated Pull Request have passed.