terraform-aws-dynamic-subnets

what

• Fix README
• Fix make targets

why

• Use standard README template
• Use / instead of : in make targets

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.

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 https://github.com/cloudposse/terraform-aws-jenkins/issues/11.

Add Continuous Integration

what

• Validate terraform code
• Add build status badge

why

• Improve code quality/consistency

Add Flag to Enable/Disable NAT Gateway

what

• Permit NAT Gateway to be disabled

why

• Sometimes only public subnets will be used. If that's the case, the NAT gateways do not provide any value and add additional cost.

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

Place NAT Gateways into public subnets

Update tf_subnets with cidr_block input