Releases: cloudposse/terraform-aws-vpc-peering-multi-account
Releases · cloudposse/terraform-aws-vpc-peering-multi-account
0.7.0: Updates to ChatOps - Automated commit (#18)
## 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.6.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
andterratest
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
0.5.0 Add description for IAM role, policy and permissions required for requester and accepter
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
0.4.0 Add example usage
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
0.3.0 Allow VPC peering when accepter doesn't have 1:1 subnet to routing table mapping
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
0.2.0 Allow for DNS resolution across VPC peers spanning multiple accounts
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
0.1.0: Initial implementation (#1)
* accepter/requester vpc peering