v0.24.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#39)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.24.0

Upgrade ecs-web-app module and support using private repository @maeghan-porter (#38)

what

• Upgrade the ecs-web-app module version to the latest and support the usage of private repositories by allowing the user to pass in private repository credentials for ecs to use.

why

• Private image repositories are an option to use and so this module should provider the ability to use them by allowing setting of the credentials on the task definition.

v0.23.0

Add use_alb_security_group flag @maeghan-porter (#37)

what

• Adding the use_alb_security_group flag to pass along to the ecs-web-app module so that a security group ingress rule will be added to the service for the ALB.

why

• The service needs to allow access from the ALB else the connectivity from ALB to atlantis will not work. This functionality was lost for me in an upgrade from version 0.14.0 of this module to the latest version (0.22.0).

v0.22.0

Make vars sensitive @kevcube (#36)

cloudposse/terraform-aws-ecs-web-app#113 <-- That PR broke this module.

what

• mark sensitive outputs sensitive

why

• current module doesn't work with tf 0.14

Error: Output refers to sensitive values

  on outputs.tf line 46:
  46: output "container_definition_json" {

Expressions used in outputs can only refer to sensitive values if the
sensitive attribute is true.


Error: Output refers to sensitive values

  on outputs.tf line 51:
  51: output "container_definition_json_map" {

Expressions used in outputs can only refer to sensitive values if the
sensitive attribute is true.

v0.21.2

🤖 Automatic Updates

Update Terraform cloudposse/ecs-web-app/aws to v0.54.0 @renovate (#33)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ecs-web-app/aws (source)	terraform	minor	0.53.1 -> 0.54.0

---

Release Notes

cloudposse/terraform-aws-ecs-web-app

v0.54.0

Compare Source

fix: make required outputs sensitive @​syphernl (#​113)

##### what * Marks the outputs sensitive to be compatible with TF 0.14 ##### why * Otherwise TF 0.14 would give an `Error: Output refers to sensitive values` when using this module ##### references * https://www.terraform.io/upgrade-guides/0-14.html#sensitive-values-in-plan-output

v0.53.7

Compare Source

🤖 Automatic Updates

chore(deps): update terraform cloudposse/ecs-cloudwatch-sns-alarms/aws to v0.12.1 @​renovate (#​118)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ecs-cloudwatch-sns-alarms/aws (source)	terraform	patch	0.12.0 -> 0.12.1

---

Release Notes

cloudposse/terraform-aws-ecs-cloudwatch-sns-alarms

##### [`v0.12.1`](https://togithub.com/cloudposse/terraform-aws-ecs-cloudwatch-sns-alarms/releases/0.12.1)

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/label/null to v0.24.1 @​&#​8203;renovate (#&#​8203;26)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	terraform	minor	0.22.1 -> 0.24.1

---

Release Notes

cloudposse/terraform-null-label

##### [`v0.24.1`](https://togithub.com/cloudposse/terraform-null-label/releases/0.24.1)

Compare Source

Allow control of letter case of outputs @​&#​8203;&#&#​8203;8203;SweetOps (#&#&#​8203;8203;107)

You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.

Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.

• You can set label_key_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
• You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.

One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".

Include updates to exports/context.tf @​&#​8203;&#&#​8203;8203;Nuru (#&#&#​8203;8203;122 and #&#&#​8203;8203;123)

##### what - Include updates to `exports/context.tf` - Update README with features and compatibilty - Add validation for `id_length_limit` ##### why - The `exports/context.tf` is what gets distributed and needs to be in sync - Replace outdated information - Was not validated earlier because validators are not supported in TF 0.12 but now we are dropping support for TF 0.12 and so we can add validators

Restore backward compatibility with v0.22.1 and earlier @​&#​8203;&#&#​8203;8203;Nuru (#&#&#​8203;8203;121)

##### what - Restore backward compatibility with v0.22.1 and earlier - Allow setting of `label_key_case` and `label_value_case` by vars, not just by context attributes. ##### why - Allow interoperability of old and new modules - Normally, root modules make settings via individual variables, not by setting an entire context block.

Incorporates and closes #&#&#​8203;8203;120

##### [`v0.24.0`](https://togithub.com/cloudposse/terraform-null-label/releases/0.24.0)

Compare Source

Restore backward compatibility with v0.22.1 and earlier @​&#​8203;&#&#​8203;8203;Nuru (#&#&#​8203;8203;121)

##### what - Restore backward compatibility with v0.22.1 and earlier - Allow setting of `label_key_case` and `label_value_case` by vars, not just by context attributes. ##### why - Allow interoperability of old and new modules - Normally, root modules make settings via individual variables, not by setting an entire context block.

Incorporates and closes #&#&#​8203;8203;120

Allow control of letter case of outputs @​&#​8203;&#&#​8203;8203;SweetOps (#&#&#​8203;8203;107)

You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.

Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.

• You can set label_key_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
• You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.

One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".

##### Known issues - `exports/context.tf` still not backwards compatible - Validation for `id_length` not included in `exports/context.tf` ##### [`v0.23.0`](https://togithub.com/cloudposse/terraform-null-label/releases/0.23.0)

[Compare Source](https://togithub...

v0.21.1

🤖 Automatic Updates

Update Terraform cloudposse/ecs-web-app/aws to v0.53.1 @renovate (#32)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ecs-web-app/aws (source)	terraform	patch	0.53.0 -> 0.53.1

---

Release Notes

cloudposse/terraform-aws-ecs-web-app

v0.53.1

Compare Source

🤖 Automatic Updates

Update context.tf @​cloudpossebot (#​111)

##### what This is an auto-generated PR that updates the `context.tf` file to the latest version from `cloudposse/terraform-null-label` ##### why To support all the features of the `context` interface.

v0.21.0

Restore correct ordering of attributes in IDs.

Support Null Label 0.24.1 @Nuru (#31)

what

• Update context.tf and dependent modules to be compatible with Null Label v0.24.1
• Drop support for Terraform 0.12

why

• New features, including restoring proper, consistent ordering of attributes in chained IDs
• Terraform 0.12 is missing important features, such as variable validation, and current version if 0.14 with 0.15 coming soon

Supersedes and replaces #28
Supersedes and replaces #29

v0.20.0 Pin GitHub provider to 3.0.0, Last Terraform 0.12 support

• Last Terraform 0.12 support
• Pin GitHub provider to 3.0.0 for bug fixes
• Remove github_webhooks_anonymous no longer supported by GitHub and causing cloudposse/terraform-aws-ecs-web-app#63

Note that this version is affected by a bug that puts attributes provided by the caller in the wrong place in some identifiers. If you are not providing attributes, it is not an issue, but if you are, please upgrade instead to v0.21.0 which has the correct order. Otherwise you may find resources being unnecessarily deleted.

Pin GitHub provider to 3.0.0 @Nuru (#30)

what

• Restore TF 0.12 support
• Remove github_anonymous
• Use modules pinned to GitHub provider 3.0.0

why

• Update/fix TF 0.12 compatible module before dropping support for TF 0.12
• GitHub provider dropped support for github_anonymous
• GitHub provider has breaking changes with every release, 3.0.0 seemed the best balance of stable, bug-free, and compatible with our codebase

v0.19.0

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#27)

what

• update context.tf to v0.23.0
• 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
• 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

v0.18.1

🤖 Automatic Updates

Update Terraform cloudposse/ecs-web-app/aws to v0.48.2 @renovate (#25)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ecs-web-app/aws (source)	terraform	patch	0.48.1 -> 0.48.2

---

Release Notes

cloudposse/terraform-aws-ecs-web-app

v0.48.2

Compare Source

🤖 Automatic Updates

chore(deps): update terraform cloudposse/alb-ingress/aws to v0.17.0 @​renovate (#​91)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/alb-ingress/aws (source)	terraform	minor	0.16.1 -> 0.17.0

---

Release Notes

cloudposse/terraform-aws-alb-ingress

##### [`v0.17.0`](https://togithub.com/cloudposse/terraform-aws-alb-ingress/releases/0.17.0)

Compare Source

fix: ensure the module does not instantiate an empty condition block @​&#​8203;jhosteny (#&#​8203;43)

Guard the creation of the condition block on the length of the optional
listener_http_header_conditions.

Fixes #&#​8203;42

what

• Make the condition blocks dynamic, requiring a non-empty list for the http headers

why

• Without this, the module attempts to create an empty condition, and fails

references

Fixes #&#​8203;42