terraform-aws-vpc-peering-multi-account

what

• Remove of enabled part of the for_each ternary, as it disables assume_role on enabled = false, which blocks teardown

why

• local.enabled ternary causes no provider to be present on enabled = false, preventing teardown

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

related

• Closes #13
• Closes #15
• Closes #11

what

• Add description for IAM role, policy and permissions required for requester and accepter

why

• Show complete and tested IAM Trust Policy and IAM Policy document with the minimum required permissions to create a VPC peering between the requester and accepter VPCs in different AWS accounts

what

• Add example usage
• Update README

why

• Shows a complete and tested example on how to use the module to create a VPC peering connection across two different AWS accounts and regions

what

• Allow VPC peering when accepter doesn't have 1:1 subnet to routing table mapping

why

• In some cases a VPC does not have 1:1 mapping between subnets and route tables

what

• Allow for DNS resolution across VPC peers spanning multiple accounts

why

• Allow accepter/requester VPC to resolve public DNS hostnames to private IP addresses when queried from instances in the requester/accepter VPC