Releases: cloudposse/terraform-aws-ec2-bastion-server
Releases · cloudposse/terraform-aws-ec2-bastion-server
0.5.1: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#31)
1. Update Version Pinning for Terraform to support 0.13 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
0.4.0: Update for Terraform 0.12 (#27)
* tf 0.12 upgrade with tests and examples * update route53 module to 0.3.0 * update label module version * add default value for security_groups var * modify DNS record * add hostname to output * add description to input * add separate sec group input variable for ingress * regenerate readme * Update example/test to us us-east-2 * Updated README.md * format example main.tf * use an ami that exists in us-east-2 in tests * Fix test CIDR checks to match updated dynamic-subnets logic Co-authored-by: actions-bot <58130806+actions-bot@users.noreply.github.com>
0.3.0
Add chatops files (#28)
0.2.7 TravisCI
what
- Add TravisCI
why
- To lint Terraform code
- To monitor build status
0.2.6 Add a parameter to configure allowed IP ranges
What
Add a parameter to configure allowed IP ranges
Why
Bastion doesn't have to be available from any IP (0.0.0.0/0)
0.2.5 Make zone_id optional
what
Make zone_id
optional
why
zone_id
parameter is declared is optional, but it really wasn't
Regenerate README.md
what
- Regenerate
README.md
why
- Previous version of build-harness has some typos
Migrate to README.yaml format
what
- Add
README.yaml
why
- Standardize README
0.2.2: Add Instance ID to outputs (#8)
* Added instance id * Fixed typo