Releases: cloudposse/terraform-aws-dynamic-subnets
Releases · cloudposse/terraform-aws-dynamic-subnets
0.3.7
Migrate to README.yaml format
what
- Add
README.yaml
why
- Standardize README
0.3.5
what
- Allows the ability to override the max number of subnets to create.
why
For some regions with many availability zones the amount of subnets gets extreme. This allows the ability to override the max number of subnets to create. Still defaults to all if nothing is supplied.
0.3.4
0.3.3
what
- Removed
provider "aws"
why
- Not necessary here, should be used in higher-level modules
- Prevents inheriting provider settings from higher-level modules
- Becomes an issue when testing locally if we use the AWS security keys like this (not the best practice, but people use it for testing):
provider "aws" {
region = "${var.region}"
access_key = "XXXXXXXXXXXXX"
secret_key = "XXXXXXXXXXXXX"
}At the same time, this code in terraform-aws-dynamic-subnets:
provider "aws" {
region = "${var.region}"
}throws the error:
module.subnets.provider.aws: No valid credential sources found for AWS Provider.
0.3.2
what
- Losen version constraint
why
- This is the change in required version syntax in order to be able to work with the Terraform Jenkins module
- it is related to the issue cloudposse-archives/terraform-aws-jenkins#11.
0.3.1
0.3.0
0.2.3
what
- Rename repo
why
- To conform to community standard: https://www.terraform.io/docs/registry/modules/publish.html
Get the Internet Gateway attached to the VPC from AWS as a data source
Get the Internet Gateway attached to the VPC from AWS as a data source