v0.12.0

Feat: Context tags for subnets and routetables @brad-haynes (#42)

what

• Context tags added to private and public subnets
• Context tags added to private and public route tables

why

• Tags were not being passed from context to the subnets and route tables

references

• No supporting issues/documentation

v0.11.3

🚀 Enhancements

Chore: Use `context.tf` from `null-label:0.25.0` @nitrocode (#41)

what

• Use context 0.25.0
• make github/init

why

• Allow tenant usage

references

N/A

v0.11.2

🤖 Automatic Updates

Update Terraform cloudposse/label/null to v0.25.0 @renovate (#39)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	module	minor	0.24.1 -> 0.25.0

---

Release Notes

cloudposse/terraform-null-label

v0.25.0

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @​Nuru (#​132)

##### what - Add additional label and `id` component: `tenant` - New input `labels_as_tags` controls which labels are exported as tags - New input `descriptor_formats` generates new output `descriptors` - Update README, remove link to obsolete `terraform-terraform-label` ##### why - Support users that host resources on behalf of and/or dedicated to single customers - Supersedes and closes #​131, giving people control over which tags the module generates - Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of `null-label` - Document `tenant`, `labels_as_tags`, `descriptor_formats`, add additional clarification, stop promoting obsolete module

Fix: Update README Snippets @​korenyoni (#​130)

##### what * Update README snippets to reflect use of Terraform Registry. ##### why * Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module. * README is out of date and does not include snippets that reflect use of the Terraform Registry. ##### references * N/A

Bridgecrew compliance @​Nuru (#​125)

##### what - Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31) - Fix typo in README - Include Terraform lock file in `.gitignore` ##### why - Get clean Bridgecrew badge - Correct confusing error - Ensure lock files are not checked into GitHub ##### note The PR can and should be merged into `master` to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to `master` will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

Properly output descriptors of chained modules @​Nuru (#​133)

##### what - Properly output descriptors of chained modules ##### why - Bug fix; implement intended behavior

v0.11.1

🐛 Bug Fixes

Fix nat_gateway_id network_interface_id variable defaults conflict @3h4x (#36)

what

• Convert input values of "" for eni_id, igw_id, and ngw_id to null before passing them to aws_route
• Correct the documentation to properly reflect that it is eni_id and not igw_id that conficts with ngw_id
• Add smoke test for creating private subnets with NAT gateway

why

• For aws_route specifying both network_interface_id and nat_gateway_id is not valid. Prior to Terraform AWS Provider 3.34.0, a value of "" was treated as "not present" so, for example, specifying a valid nat_gateway_id and a network_interface_id = "" was accepted. With 3.34.0, however, "" is interpreted as a value by and triggers the error:

     "vpc_endpoint_id": only one of `egress_only_gateway_id,gateway_id,instance_id,local_gateway_id,nat_gateway_id,network_interface_id,transit_gateway_id,vpc_endpoint_id,vpc_peering_connection_id`
      can be specified, but `nat_gateway_id,network_interface_id` were specified.

• In this module igw_id is only used in the route table for the public subnets, so it does not conflict with eni_id origw_id which are only used in the rout table for the private subnets.
• Catch this problem if it recurs

references

• closes #35
• hashicorp/terraform-provider-aws v3.34.0 release notes
• hashicorp/terraform-provider-aws PR changing behavior of aws_route

v0.11.0

tag the eip for the nat gateway @ekristen (#34)

what

• apply the same tags to the aws_eip for the nat_gateway as the other resources

why

• naming and tagging consistency
• to be able to know that the EIP allocated was for the NAT gateway

v0.10.0

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

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

Supersedes and closes #30
Supersedes and closes #31

v0.9.2

🤖 Automatic Updates

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

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

🚀 Enhancements

Terraform 0.14 upgrade @maximmi (#27)

what

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

why

• Support Terraform 0.14

Supersedes and closes #26
Supersedes and closes #29

0.9.0 update to context

what

• Update to context.tf

why

• Standardization and interoperability

0.8.0: Add map_public_ip_on_launch variable (#23)

## what
* Support `map_public_ip_on_launch` for public subnets

## why
* This is most useful when deploying public subnets with `nat_enabled = false`