0.5.1: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#21)

## What

1. Update Version Pinning for Terraform to support 0.13

## Why

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

0.5.0: [AUTOMATED] Update terraform-null-label versions to support Terraform…

… 0.13 (#22)

* [AUTOMATED] Update terraform-null-label versions to support Terraform 0.13

* Updated README.md

Co-authored-by: actions-bot <[email protected]>

0.4.0: Updates to ChatOps - Automated commit (#20)

## What
* Adds chatops commands
  - '/test all'
  - '/test bats'
  - '/test readme'
  - '/test terratest'
* Drops codefresh
* Drops slash-command-dispatch
* Removes codefresh badge
* Rebuilds README

## Why
* Change over from codefresh to GH Actions
* Facilitate testing of PRs from forks

0.3.0 Convert to TF 0.12. Add tests. Add Codefresh test pipeline

what

• Port module to Terraform 0.12
• Pin all providers
• Add example for testing
• Add bats and terratest for the example
• Add Codefresh badge to point to the test pipeline in terraform-modules project
• Update README

why

• Module currently does not work with 0.12. Much easier syntax
• Better regression control
• Automatically test the example on every commit and pull request
• Provision resources on AWS in the test account and check the outputs for the correct values
• terraform-modules project contains pipelines for all terraform modules

0.2.0: Added tags to find vpc (#10)

* Added tags to find vpc

* Added tags to find vpc

* Apply suggestions from code review

Co-Authored-By: goruha <[email protected]>

* Address comments

* Address comments

* Address comments

0.1.4: Update readme yaml file (#7)

* doc: update readme yaml file
- add tags and categories

* feature: update readme yaml and rebuild readme md

* feature: resolve review issue
- delete ecommerce tag

0.1.3

what

Enables users to add all the CIDRs (primary and secondaries) to the created route tables.
https://www.terraform.io/docs/providers/aws/d/vpc.html#cidr_block-1

why

AWS provided the ability to extend VPCs with secondary CIDRs
https://aws.amazon.com/about-aws/whats-new/2017/08/amazon-virtual-private-cloud-vpc-now-allows-customers-to-expand-their-existing-vpcs/

Migrate to README.yaml format

what

• Add README.yaml

why

• Standardize README

0.1.1

what

• Fix eventual consistency issues

why

• The module could not find the Route it just created in the same session

* aws_route.requestor: 1 error(s) occurred:

* aws_route.requestor: Error finding route after creating it: 

Unable to find matching route for Route Table (rtb-f40f0c93) and destination CIDR block (10.0.0.0/16).

references

• hashicorp/terraform#9756
• hashicorp/terraform#7038
• hashicorp/terraform#8226
• hashicorp/terraform#5335

0.1.0

what

• Terraform module to create a peering connection between two VPCs

why

• To allow VPCs to communicate