Releases: cloudposse/terraform-aws-vpc
Releases · cloudposse/terraform-aws-vpc
0.4.1 Fix example with CIDR
what
- Fix example with CIDR
why
- CIDR was not given in example, but it is required
0.4.0 Remove default VPC CIDR range
what
- Remove default VPC CIDR range
why
- Better to declare the CIDR rather than default to use 10.0.0.0
0.3.6: Add example usage (#21)
* feat(examples): add basic example * Update namespace description in basic example * Create cidr_block variable in basic example Use it in both modules * Move default values from variables.tf to terraform.tfvars - set subnets nat_gateway_enabled as false - check on geodesic * Rename tfvars file
0.3.5 Update readme yaml file and rebuild md
what
- updated
README.yaml
file - add tags and categories
- rebuild
README.md
file
why
- need to add categories and tags so we can pull them into the documentation
Migrate to README.yaml format
what
- Add
README.yaml
why
- Standardize README
0.3.3
what
- Force
assign_generated_ipv6_cidr_block
why
- To address the issue #15
- To fix Terraform errors if
assign_generated_ipv6_cidr_block
is set tofalse
* module.vpc.output.vpc_ipv6_association_id: Resource 'aws_vpc.default' does not have attribute 'ipv6_association_id' for variable 'aws_vpc.default.ipv6_association_id'
* module.vpc.output.ipv6_cidr_block: Resource 'aws_vpc.default' does not have attribute 'ipv6_cidr_block' for variable 'aws_vpc.default.ipv6_cidr_block'
- Assigning an IPv6 CIDR block to VPC does not consume any additional resources and does not cost anything
0.3.2
0.3.1
Remove subnets module
What
- Exclude
terraform-aws-dynamic-subnets
module - Update README
Why
- Provision only general VPC components with
terraform-aws-vpc
- Make
subnets
module plugable (e.g. we would be able to use anysubnets
module withterraform-aws-dynamic-subnets
module)
Add `attributes` and `tags` to modules
What
- Added
attributes
andtags
to modules
Why
- So we could assign arbitrary tags to AWS resources