terraform 0.12.0

.gitignore

@@ -0,0 +1,6 @@
+# ignored files
+*.tfstate
+*.tfstate.backup
+.terraform
+.idea
+*.iml

.pre-commit-config.yaml

@@ -0,0 +1,13 @@
+repos:
+  - repo: git://github.com/antonbabenko/pre-commit-terraform
+    rev: v1.12.0
+    hooks:
+    - id: terraform_fmt
+
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v2.0.0
+    hooks:
+      - id: check-merge-conflict
+      - id: trailing-whitespace
+      - id: check-yaml
+      - id: check-added-large-files

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 Cloud Drove
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

Makefile

@@ -0,0 +1,3 @@
+export GENIE_PATH ?= $(shell 'pwd')/../../../genie
+
+include $(GENIE_PATH)/Makefile

README.md

@@ -1 +1,140 @@
-# terraform-aws-vpc-peering
+<!-- This file was automatically generated by the `geine`. Make all changes to `README.yaml` and run `make readme` to rebuild this file. -->
+
+<p align="center"> <img src="https://user-images.githubusercontent.com/50652676/62349836-882fef80-b51e-11e9-99e3-7b974309c7e3.png" width="100" height="100"></p>
+
+
+<h1 align="center">
+    Terraform AWS VPC Peering
+</h1>
+
+<p align="center" style="font-size: 1.2rem;">
+    Terraform module to connect two VPC's on AWS.
+     </p>
+
+<p align="center">
+
+<a href="https://www.terraform.io">
+  <img src="https://img.shields.io/badge/Terraform-v0.12-green" alt="Terraform">
+</a>
+<a href="LICENSE.md">
+  <img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="Licence">
+</a>
+
+
+</p>
+<p align="center">
+
+<a href='https://facebook.com/sharer/sharer.php?u=https://github.com/clouddrove/terraform-aws-vpc-peering'>
+  <img title="Share on Facebook" src="https://user-images.githubusercontent.com/50652676/62817743-4f64cb80-bb59-11e9-90c7-b057252ded50.png" />
+</a>
+<a href='https://www.linkedin.com/shareArticle?mini=true&title=Terraform+AWS+VPC+Peering&url=https://github.com/clouddrove/terraform-aws-vpc-peering'>
+  <img title="Share on LinkedIn" src="https://user-images.githubusercontent.com/50652676/62817742-4e339e80-bb59-11e9-87b9-a1f68cae1049.png" />
+</a>
+<a href='https://twitter.com/intent/tweet/?text=Terraform+AWS+VPC+Peering&url=https://github.com/clouddrove/terraform-aws-vpc-peering'>
+  <img title="Share on Twitter" src="https://user-images.githubusercontent.com/50652676/62817740-4c69db00-bb59-11e9-8a79-3580fbbf6d5c.png" />
+</a>
+
+</p>
+<hr>
+
+
+We eat, drink, sleep and most importantly love **DevOps**. We are working towards stratergies for standardizing architecture while ensuring security for the infrastructure. We are strong believer of the philosophy <b>Bigger problems are always solved by breaking them into smaller manageable problems</b>. Resonating with microservices architecture, it is considered best-practice to run database, cluster, storage in smaller <b>connected yet manageable pieces</b> within the infrastructure.
+
+This module is basically combination of [Terraform open source](https://www.terraform.io/) and includes automatation tests and examples. It also helps to create and improve your infrastructure with minimalistic code instead of maintaining the whole infrastructure code yourself.
+
+We have [*fifty plus terraform modules*][terraform_modules]. A few of them are comepleted and are available for open source usage while a few others are in progress.
+
+
+
+
+## Prerequisites
+
+This module has a few dependencies:
+
+- [Terraform 0.12](https://learn.hashicorp.com/terraform/getting-started/install.html)
+- [Go](https://golang.org/doc/install)
+- [github.com/stretchr/testify/assert](https://github.com/stretchr/testify)
+- [github.com/gruntwork-io/terratest/modules/terraform](https://github.com/gruntwork-io/terratest)
+
+
+
+
+
+
+## Examples
+
+**IMPORTANT:** Since the `master` branch used in `source` varies based on new modifications, we suggest that you use the release versions [here](https://github.com/clouddrove/terraform-aws-vpc-peering/releases).
+
+
+### Simple Example
+Here is an example of how you can use this module in your inventory structure:
+```hcl
+  module "vpc-peering" {
+      source            = "git::https://github.com/clouddrove/terraform-aws-vpc-peering.git"
+      name              = "vpc-peering"
+      application       = "clouddrove"
+      environment       = "test"
+      label_order       = ["environment", "name", "application"]
+      requestor_vpc_id  = "vpc-XXXXXXXXXXXXXXXXX"
+      acceptor_vpc_id   = "vpc-XXXXXXXXXXXXXXXXX"
+    }
+```
+
+
+
+## Inputs
+
+| Name | Description | Type | Default | Required |
+|------|-------------|:----:|:-----:|:-----:|
+| acceptor_allow_remote_vpc_dns_resolution | Allow acceptor VPC to resolve public DNS hostnames to private IP addresses when queried from instances in the requestor VPC. | bool | `true` | no |
+| acceptor_vpc_id | Acceptor VPC ID. | string | - | yes |
+| application | Application (e.g. `cd` or `clouddrove`). | string | `` | no |
+| auto_accept | Automatically accept the peering (both VPCs need to be in the same AWS account). | bool | `true` | no |
+| environment | Environment (e.g. `prod`, `dev`, `staging`). | string | `` | no |
+| label_order | label order, e.g. `name`,`application`. | list | `<list>` | no |
+| name | Name  (e.g. `app` or `cluster`). | string | `` | no |
+| requestor_allow_remote_vpc_dns_resolution | Allow requestor VPC to resolve public DNS hostnames to private IP addresses when queried from instances in the acceptor VPC. | bool | `true` | no |
+| requestor_vpc_id | Requestor VPC ID. | string | - | yes |
+| tags | Additional tags (e.g. map(`BusinessUnit`,`XYZ`). | map(string) | `<map>` | no |
+| vpc_peering | Set to false to prevent the module from creating or accessing any resources. | bool | `true` | no |
+
+## Outputs
+
+| Name | Description |
+|------|-------------|
+| accept_status | The status of the VPC peering connection request. |
+| connection_id | VPC peering connection ID. |
+| tags | A mapping of tags to assign to the resource. |
+
+
+
+## Testing
+
+In this module testing is performed with [terratest](https://github.com/gruntwork-io/terratest) and it creates a small piece of infrastructure, matches the output like ARN, ID and Tags name etc and destroy infrastructure in your AWS account. This testing is written in GO, so you need a [GO environment](https://golang.org/doc/install) in your system.
+
+You need to run the following command in the testing folder:
+```hcl
+  go test -run Test
+```
+
+
+
+## Feedback
+If you come accross a bug or have any feedback, please log it in our [issue tracker](https://github.com/clouddrove/terraform-aws-vpc-peering/issues), or feel free to drop us an email at [hello@clouddrove.com](mailto:hello@clouddrove.com).
+
+If you have found it worth your time, go ahead and give us a ★ on [our GitHub](https://github.com/clouddrove/terraform-aws-vpc-peering)!
+
+## About us
+
+At [CloudDrove][website], we offer expert guidance, implementation support and services to help organisations accelerate their journey to the cloud. Our services include docker and container orchestration, cloud migration and adoption, infrastructure automation, application modernisation and remediation, and performance engineering.
+
+<p align="center">We are <b> The Cloud Experts!</b></p>
+<hr />
+<p align="center">We ❤️  <a href="https://github.com/clouddrove">Open Source</a> and you can check out <a href="https://github.com/clouddrove">our other modules</a> to get help with your new Cloud ideas.</p>
+
+  [website]: https://clouddrove.com
+  [github]: https://github.com/clouddrove
+  [linkedin]: https://cpco.io/linkedin
+  [twitter]: https://twitter.com/clouddrove/
+  [email]: https://clouddrove.com/contact-us.html
+  [terraform_modules]: https://github.com/clouddrove?utf8=%E2%9C%93&q=terraform-&type=&language=

README.yaml

@@ -0,0 +1,47 @@
+---
+#
+# This is the canonical configuration for the `README.md`
+# Run `make readme` to rebuild the `README.md`
+#
+
+# Name of this project
+name : Terraform AWS VPC Peering
+
+# License of this project
+license: "MIT"
+
+# Canonical GitHub repo
+github_repo: clouddrove/terraform-aws-vpc-peering
+
+# Badges to display
+badges:
+  - name: "Terraform"
+    image: "https://img.shields.io/badge/Terraform-v0.12-green"
+    url: "https://www.terraform.io"
+  - name: "Licence"
+    image: "https://img.shields.io/badge/License-MIT-blue.svg"
+    url: "LICENSE.md"
+
+#  description of this project
+description: |-
+  Terraform module to connect two VPC's on AWS.
+
+# extra content
+include:
+  - "terraform.md"
+
+# How to use this project
+usage : |-
+  ### Simple Example
+  Here is an example of how you can use this module in your inventory structure:
+  ```hcl
+    module "vpc-peering" {
+        source            = "git::https://github.com/clouddrove/terraform-aws-vpc-peering.git"
+        name              = "vpc-peering"
+        application       = "clouddrove"
+        environment       = "test"
+        label_order       = ["environment", "name", "application"]
+        requestor_vpc_id  = "vpc-XXXXXXXXXXXXXXXXX"
+        acceptor_vpc_id   = "vpc-XXXXXXXXXXXXXXXXX"
+      }
+  ```

_example/example.tf

@@ -0,0 +1,15 @@
+provider "aws" {
+  region = "eu-west-1"
+}
+
+module "vpc-peering" {
+  source = "git::https://github.com/clouddrove/terraform-aws-vpc-peering.git"
+
+  name        = "vpc-peering"
+  application = "clouddrove"
+  environment = "test"
+  label_order = ["environment", "name", "application"]
+
+  requestor_vpc_id = "vpc-XXXXXXXXXXXXXXXXX"
+  acceptor_vpc_id  = "vpc-XXXXXXXXXXXXXXXXXcd"
+}

_example/outputs.tf

@@ -0,0 +1,11 @@
+#Module      : VPC PEERING
+#Description : Terraform vpc peering module output variables.
+output "accept_status" {
+  value       = module.vpc-peering.accept_status
+  description = "The status of the VPC peering connection request."
+}
+
+output "tags" {
+  value       = module.vpc-peering.tags
+  description = "A mapping of tags to assign to the VPC Peering."
+}

_test/vpcpeering_test.go

@@ -0,0 +1,35 @@
+// Managed By : CloudDrove
+// Description : This Terratest is used to test the Terraform VPC module.
+// Copyright @ CloudDrove. All Right Reserved.
+package test
+
+import (
+	"testing"
+	"github.com/stretchr/testify/assert"
+	"github.com/gruntwork-io/terratest/modules/terraform"
+)
+
+func Test(t *testing.T) {
+	t.Parallel()
+
+	terraformOptions := &terraform.Options{
+
+		// Source path of Terraform directory.
+		TerraformDir: "../_example",
+		Upgrade: true,
+	}
+
+	// This will run 'terraform init' and 'terraform application' and will fail the test if any errors occur
+	terraform.InitAndApply(t, terraformOptions)
+
+	// To clean up any resources that have been created, run 'terraform destroy' towards the end of the test
+	defer terraform.Destroy(t, terraformOptions)
+
+	// To get the value of an output variable, run 'terraform output'
+	Status := terraform.Output(t, terraformOptions, "accept_status")
+	Tags := terraform.OutputMap(t, terraformOptions, "tags")
+
+	// Check that we get back the outputs that we expect
+	assert.Equal(t, "test-vpc-peering-clouddrove", Tags["Name"])
+	assert.Contains(t, Status, "active")
+}