v0.17.9

This release improperly tags the ASG, do not use.

🚀 Enhancements

Fix ASG tags @martinhaus (#63)

what

Fixes #62

The ASG was not properly tagged and the workers were not able to join the cluster due to a missing tag with "kubernetes.io/cluster/${var.cluster_name}" = "owned"

Merges var.autoscaling_group_tags with module.label.tags

references

closes #62

v0.17.8

🤖 Automatic Updates

chore(deps): update terraform cloudposse/ec2-autoscale-group/aws to v0.22.0 @renovate (#60)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ec2-autoscale-group/aws (source)	terraform	minor	0.14.0 -> 0.22.0

---

Release Notes

cloudposse/terraform-aws-ec2-autoscale-group

v0.22.0

Compare Source

Update example subnet module @​nitrocode (#​62)

#### what * Upgraded subnet module to latest https://github.com/cloudposse/terraform-aws-dynamic-subnets #### why * Looks like it's causing issues with bridgecrew #### references * N/A

v0.21.0

Compare Source

Expose metadata HTTP tokens @​alexjurkiewicz (#​56)

Expose aws_launch_template -> metadata_options -> http_tokens.

v0.20.0

Compare Source

add desired_capacity settings @​dmitriy-lukyanchikov (#​37)

#### what - add desired_capacity settings #### why - sometimes useful to set add `var.desired_capacity` #### references * closes https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/issues/29

v0.19.0

Compare Source

Feature/additional tag specifications @​tthayer (#​34)

#### what * Adds additional tag_specification blocks #### why * Spot requests are not currently getting tagged #### references * https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/launch_template#tag-specifications

v0.18.0

Compare Source

readme: Add block_device_mappings example @​nitrocode (#​59)

#### what * Provide a basic example of `var.block_device_mappings` provided by @​kskewes #### why * It's not clear how to use `var.block_device_mappings` and this should clear it up #### references * Should close https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/issues/18

v0.17.0

Compare Source

Add max_instance_lifetime @​nitrocode (#​61)

#### what * Add max_instance_lifetime #### why * This allows a maximum amount of time that an instance can be in service. With this value set, we can make sure that these instances will rotate after a certain period of time. #### references N/A

v0.16.2

Compare Source

🚀 Enhancements

var.use_name_prefix @​nitrocode (#​60)

#### what * Toggles between `name` and `name_prefix` asg arguments * Affects `aws_autoscaling_group` and not the `aws_launch_template`

Followed similar

https://github.com/cloudposse/terraform-aws-security-group/blob/c090804ba938edf434b660e771527ce7d94a52f4/main.tf#L4-L5

why

• To backport existing resources to use this module without recreating resources

references

• Closes #​28

v0.16.1

Compare Source

🚀 Enhancements

readme: Change string bool to bool @​nitrocode (#​57)

#### what * Tiny changes in readme #### why * `> tf 12` appeal #### references N/A

v0.16.0

Compare Source

Fix README formatting @​alexjurkiewicz (#​54)

#### what * Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?) * Use bullet points to be concise and to the point. #### why * Provide the justifications for the changes (e.g. business case). * Describe why these changes were made (e.g. why do these commits fix the problem?) * Use bullet points to be concise and to the point. #### references * Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow). * Use `closes #​123`, if this PR closes a GitHub issue `#123`

v0.15.0

Compare Source

Add support for the instance_refresh block @​msmagoo87 (#​53)

#### what * Add support for the instance_refresh block (https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group#instance_refresh) #### why * Allow the specification of an instance refresh criteria on the Autoscaling Group

---

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.

v0.17.7

🤖 Automatic Updates

chore(deps): update terraform cloudposse/ec2-autoscale-group/aws to v0.14.0 @renovate (#59)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ec2-autoscale-group/aws (source)	terraform	minor	0.13.1 -> 0.14.0

---

Release Notes

cloudposse/terraform-aws-ec2-autoscale-group

v0.14.0

Compare Source

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @​maximmi (#​51)

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

v0.17.6

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.24.1 @renovate (#58)

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

Compare Source

Allow control of letter case of outputs @​SweetOps (#​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 @​Nuru (#​122 and #​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 @​Nuru (#​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 #​120

v0.24.0

Compare Source

Restore backward compatibility with v0.22.1 and earlier @​Nuru (#​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 #​120

Allow control of letter case of outputs @​SweetOps (#​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

Compare Source

Known issues

• Does not interoperate with earlier versions of null-label. The canonical context = module.this.context fails if module.this.context is an older version
• context.tf does not incorporate var.label_key_case and var.label_value_case into the module.this object, preventing those variables from taking effect in the root module's module.this.

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

v0.17.5

🤖 Automatic Updates

chore(deps): update terraform cloudposse/ec2-autoscale-group/aws to v0.13.1 @renovate (#50)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ec2-autoscale-group/aws (source)	terraform	minor	0.12.0 -> 0.13.1

---

Release Notes

cloudposse/terraform-aws-ec2-autoscale-group

v0.13.1

Compare Source

🤖 Automatic Updates

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

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

Compare Source

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

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

Compare Source

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​49)

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

🤖 Automatic Updates

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#56)

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

v0.17.3

🤖 Automatic Updates

Update context.tf @cloudpossebot (#57)

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.17.2

🤖 Automatic Updates

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

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.17.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#54)

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.17.0

Terraform 0.14 upgrade @maximmi (#52)

what

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

why

• Support Terraform 0.14

supersedes and closes #48
supersedes and closes #37
supersedes and closes #33