* add vars for custom subnet and route table names

* revert db suffix to "db"

* Add secondary CIDR block support using a local variable to derive the vpc id to ensure the CIDR block operations are applied before the CIDR operations

* Add secondary cidr block outputs to module output

* Add the wonderful examples from matthiasr's PR located at https://github.com/terraform-aws-modules/terraform-aws-vpc/pull/162 all credit goes to them for this wonderful example

* From copy and paste accidentally used variable name that differed from these variables

* Resolve typo in secondary_cidr_blocks

* Fixed README formatting

* Followups for #161

* Added local.vpc_id with description

* Added support for IPv6 to VPC

* Provide separate route tables for db/elasticache/redshift

* Added example for saperate routes

* Updated PR with suggestions

* Make redshift to use separate subnet route table also

* More cleanup and updates

* Fixed one more spelling mistake

just a typo in the docs and in the
public_subnet_tags in the simple example

* Allow tags override for all resources (fix for #138)

* Added tags for all resources which were missing them

Fixed creation of aws_vpc_endpoint_route_table_association when intra_subnets are not set (fixes 137)

* Adding Lambda subnets for serverless functions that need to communicate
within the VPC

* Switched to "infra_subnet" for a private subnet without NAT gateway.

* Fixing typo - removing last "lambda" ref.

* Added README docs on intra subnets, and added it to complete VPC
example.  Fixed naming.

* Initial commit for issue #117

* Adding documentation for NAT Gateway creation

* Adding `enable_nat_gateway` to the documentation

* Updating README.md with `one_nat_gateway_per_az` to be 'true' by default

* Reverted changes back to `one_nat_gateway_per_az` as 'false'

Fixes #82

* Ensures the S3 VPC Endpoint association is only created if there are public subnets

Fixes #89

* Ensures a single DDB association in the public route table

Removed aws_default_route_table and aws_main_route_table_association, added potentially failed example (#111)

* Extended aws_vpn_gateway use case

* Fixed warning from outputs on vgw_id

* Added possibility to create VPC conditionally

* Added editorconfig and pre-commit hooks

* Manage Default Route Table under Terraform

- With name
- And Tags

* Use `aws_default_route_table` instead

* Added aws_main_route_table_association resource

* Update main.tf

* Adding base-level tests for simple-example

* gitignoring test kitchen internals

* incorporating feedback from newcontext folks

* comment clean up before PR

* upgrading to kt 3.1.x

* test repaired for kt 3 compat

* removing the gemfile lock

* making md linter happy and adjusting content to match test fixture

* PR feedback and rubocop compliance

* Issue #56: Added tags for elastic ips

* add cidr_block outputs to public and private subnets

* add cidr_block outputs to database and elasticache subnets

* add redshift subnet option

* fix tag

* add missing route association for redshift

* add vpc_endpoint_s3_pl_id and vpc_endpoint_dynamodb_pl_id outputs

* add redshift to complete-vcp example

* fix domain_name_servers - keep it a list

* fix outputs for TF 0.11

* fix missing *

* Minor corrections in example and in type of dhcp_options_domain_name_servers

* Minor corrections in example

* Updated README

[CodeTriage](https://www.codetriage.com/) is an app I have maintained
for the past 4-5 years with the goal of getting people involved in
Open Source projects like this one. The app sends subscribers a random
open issue for them to help "triage". For some languages you can also
suggested areas to add documentation.

The initial approach was inspired by seeing the work of the small
core team spending countless hours asking "what version was
this in" and "can you give us an example app". The idea is to
outsource these small interactions to a huge team of volunteers
and let the core team focus on their work.

I want to add a badge to the README of this project. The idea is to
provide an easy link for people to get started contributing to this
project. A badge indicates the number of people currently subscribed
to help the repo. The color is based off of open issues in the project.

Here are some examples of other projects that have a badge in their
README:

- https://github.com/crystal-lang/crystal
- https://github.com/rails/rails
- https://github.com/codetriage/codetriage

Thanks for building open source software, I would love to help you find some helpers.