terraform-aws-ecs-alb-service-task

what

• var.subnet_ids should be optional

why

• It's only required if awsvpc is the launch_type since it's only used for aws_ecs_service's network_configuration
• This makes it easier for EC2 (non fargate) tasks

references

N/A

🚀 Enhancements

what

Fixed the HCL spacing in the README.md example

why

Because it was annoying to fix the spacing when copying and pasting

references

N/A

what

• update context.tf to v0.24.1
• 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, back compatibility with context v0.22.0 and below
• 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

🤖 Automatic Updates

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.

what

• Expose ARN for service so we don't have to manually construct it

why

• Ease of use and preventing user error

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.24.1

Compare Source

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 = "".

Incorporates and closes #​120

v0.24.0

Compare Source

Incorporates and closes #​120

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 = "".

v0.23.0

Compare Source

• feat: add support for setting letter case of context tags @​SweetOps (#​107)

With this release, you gain 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 = "".

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

🤖 Automatic Updates

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

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

what

• Update terraform-null-label to restore attribute order handling in place prior to #82

why

• Automatic merging of old attributes with new attributes was added to terraform-null-label v0.19.0 and incorporated into this module in #82. However, prior to terraform-null-label v0.22.1, it placed new attributes in front of old attributes, instead of the previous behavior of this module, which was to place new attributes at the end of the attribute list. This causes unnecessary and unwanted changes in resource names.

references

• cloudposse/terraform-null-label#113

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.22.1

Compare Source

what

• Add var.attributes to end of context.attributes, not vice versa
• Update to current workflows (with some exceptions)

why

• Modules should append to attributes passed in, not insert themselves ahead of others
• New features, like auto-format (but holding back some, because this is a special module)

references

• closes #​113
• closes #​108

🚀 Enhancements

what

• Creates two variables to accept a list of policies to attach to the generated task and task execution roles
• The policies are only attached if the the roles were created by this module.

why

• When creating services that reference outside secrets it would be easier to pass the required policy during service creation.

references

• This is related to #67 and #68
• Supersedes and closes #86

🚀 Enhancements

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

what

• In the case of registering more than one Target Group, don't create or pass the ECS service IAM role to the aws_ecs_service block.

why

• If you are registering multiple target groups to the service, you must allow ECS to create a service-linked role rather than passing one that was manually created. Passing one results in an API error from ECS: Error: InvalidParameterException: You cannot specify an IAM role for services that require a service linked role.

references

• https://docs.aws.amazon.com/AmazonECS/latest/developerguide/register-multiple-targetgroups.html

what

• Update to accept aws provider 3

why

• To make provider versions compatible

what

Description of container_definition_json is somewhat obscure regarding the possibility to use multiple container definitions. This MR addresses #69 by making this ability more explicit.

references

• Closes #69