Releases: skyscrapers/terraform-network
5.2.0
5.1.2
5.1.0
5.0.1
Refactor resource naming and tagging
Read this first
Starting with v5, we've changed how naming and tagging of resources happen within the modules. In earlier versions, a resource's name was derived from the project
and environment
variables.
Starting with v5, we only provide a name
variable, so make sure to update your code accordingly. In most cases this shouldn't be a breaking change: names for VPCs, subnets, route tables etc can be changed without a destroy/recreate of the resources.
Important: The exception is for Security Groups, so eg. in case of the securitygroups/all
module, you should specify name = "sg_all_myproject_myenv"
to keep the old name.
We've also removed our default, hardcoded tags for Project
and Environment
. You can still re-add these via the respective tags
variables, or use the default_tags
parameter from the AWS provider.
What's Changed
Full Changelog: 4.2.0...5.0.0
New vpc_peering module
4.2.0 Add vpc peering module (#27)
4.1.1
Add option to enable auto assigning public IP addresses on public subnets.
4.1.0
4.0.0 Update code to terraform 0.12
This release makes all the terraform code compatible with terraform 0.12