terraform-aws-dynamic-subnets

🚀 Enhancements

what

• Availability zones must be greater than zero

why

• To prevent accidental applies without setting zones which results in basically a no-op or setting var.enabled = false.

references

N/A

🚀 Enhancements

what

• Bump null-label module versions to 0.25.0 in order to be compatible with context.tf.
• Run make github/init

why

• The null-label modules used in this module are incompatible with new labels in context.tf (i.e. tenant) which appear in 0.25.0.
• Running make github/init updates GitHub Actions Workflows to the latest ones exported by build-harness.

references

• N/A

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

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.8.0

Compare Source

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.7.0

Compare Source

• Update the outputs to make elb_logging_account its own output

why

• In #​10 I mistakenly added this output to the region_az_alt_code_maps output

v0.6.0

Compare Source

• Add a lookup for ELB accounts for Elastic Load Balancer accounts

why

• When creating bucket policies to allow logging from ELB/ALB to write their access logs to S3, it is necessary to give permissions to the dedicated account the ELB/ALB is created in.

references

• AWS Documentation

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.5.0

Compare Source

• https://docs.aws.amazon.com/general/latest/gr/rande.html

what

• Replaced removed list function with tolist to make it work with Terraform 0.15.
• Updated Github Workflows

why

• The list function was deprecated since Terraform v0.12 and has been removed in Terraform v0.15, resulting in an Error: Error in function call.

🚀 Enhancements

what

• This PR is just to remove the unused provider in versions.tf and that will

why

• Download unused providers to terraform project
• Break projects running on Apple Silicon chip

references

• Closes #129

Remove use of deprecated map()

This function is removed in the upcoming Terraform 0.15. Since Terraform
0.12, you can create maps with a literal syntax instead.

what

• No change to module behaviour

why

Adds compatibility with Terraform 0.15. Without this, you'll see errors like:

│ Error: Error in function call
│
│   on .terraform/modules/dynamic_subnets/private.tf line 8, in module "private_label":
│    8:     map(var.subnet_type_tag_key, format(var.subnet_type_tag_value_format, "private"))
│     ├────────────────
│     │ var.subnet_type_tag_key is a string, known only after apply
│     │ var.subnet_type_tag_value_format is a string, known only after apply
│
│ Call to function "map" failed: the "map" function was deprecated in Terraform v0.12 and is no longer available; use tomap({ ... })
│ syntax to write a literal map.

🤖 Automatic Updates

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

This PR contains the following updates:

Release Notes

v0.4.0

Compare Source

Closes #​6
Closes #​7

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

🤖 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

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

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

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.3.0

Compare Source

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

• Add required http_endpoint and http_put_response_hop_limit parameters to the metadata_options section

why

• Changes done in 886a164e9e7ead17ec3076137d3e340af5eca2e3 results in a Terraform error while provisioning (A value of '' is not valid for HttpEndpoint)
• Syncs up with the settings we also use for terraform-aws-ec2-bastion-server

what

• BridgeCrew compliance checks fix
• readme updated
• code clean up
• workflows updated
• default behaviour changed: Instance Metadata Service Version 2 forced by default
• default behaviour changed: Encryption of the root block device enabled by default

why

• To be able to position our modules as standards compliant
• Providing explicit note about policy attached directly to user
• removed unnecessary providers dependencies
• to stay in sync with all repos
• To comply BridgeCrew check
• To comply BridgeCrew check

references

• https://docs.bridgecrew.io/docs/public_12
• https://docs.bridgecrew.io/docs/general_13
• https://docs.bridgecrew.io/docs/bc_aws_general_31

what

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

why

• Support Terraform 0.14