Releases: joshuamkite/terraform-aws-ssh-bastion-service
Meta-Morphosis
- Feature: EC2 instances can be supplied metadata options through
var.bastion_metadata_options
- Change: Increment required terraform version to >= 1.3.0
- Thanks: bird-bust-battery
Externalities
- Feature: Make default permissive outbound security group rule creation conditional:
var.custom_outbound_security_group
type = bool
. Historic behaviour is followed by default - Feature: Make bastion service port configurable:
var.bastion_service_port
type = number
. Historic behaviour is followed by default - Feature: Add new
examples/custom_outbound_security_group
demonstrating use of above - Change: Increment required terraform version to >= 1.2.0 since we are not testing historic versions
- Change: Increment suggested AWS provider to 4.22 (not hard enforce)
- Change: Remove obsolete explicit manual dependencies from examples
- Change: Remove obsolete quotes from interpolations in locals
- Change: Tidy up Readme to include new options sensibly
Lemniscate
- Change: Defaults to Debian 11 (host) and Ubuntu 22.04 (Container). Alternative combinations, distributions and non-AMD64 platforms not tested at this time. Tested using
- Terraform v1.1.9
- hashicorp/aws v4.12.1
- hashicorp/cloudinit v2.2.0
- Change: Moved to go mod to build golang binary (uses go1.15.15 linux/amd64 on Debian host)
- Change: Default ebs device name changed: "xvda" => "/dev/sda1"
- Change: /examples/full-with-public-ip instance type changed:
t2.micro
=>t3.micro
. t2.micro no longer completes healtchchecks successfully - Change: default instance types changed:
["t2.small", "t2.medium", "t2.large"]
=>["t3.small", "t3.medium", "t3.large"]
. t2 instance types no longer complete healtchchecks successfully - Change:
var.subnets_asg
andvar.subnets_lb
are now Required inputs. Sadly this apparently should have been the case since release 6.0 when automatic subnet selection was removed
That's My Lucky Number
Breaking changes with existing deployments using earlier module versions
- Change: Retire deprecated null-resource provider
- Change: Retire deprecated template provider (required for darwin_arm64). Fixes Issue #51
- Feature: Support provider default tags as well as explicit tags for all supported resources plus autoscaling group
- Change: Update Terraform version to >/=0.15.x/1.0.0
- Change/Feature: Change from Launch Configuration to Launch Template. Includes support for spot instances. Fixes Issue #46
- Feature: Enable setting cloudwatch metrics for autoscaling group
- Feature: Add unique target group name for bastion host elb
- Feature: Enable setting EBS size and name for bastion instance
- Bugfix: Update formatting in readme
- Bugfix: Spellcheck readme and changelog
- Change: Update terraform-docs outputs on documentation
- Change: Update internal filenames and references to comply with upstream template file naming conventions; move locals to locals.tf
Are you feeling lucky
Update readme to specify that we are targeting terraform 13
Lucky for some
Major version increment as changes accommodate major version increments for both AWS provider and Terraform itself
Updates for:
- Terraform 0.13 using
terraform 0.13upgrade
linting and provider specification - Terraform AWS provider 3.0.0 -
vpc_zone_identifier
argument now conflicts withvpc_zone_identifier
in Resource:aws_autoscaling_group
- Single deployment of included example, accommodating above changes
var.aws_profile
is now defaulted to""
as it is only used for sample policies output
Intergalactic
Bugfix: Change all apt
=> apt-get
; Prefix apt-get install
with DEBIAN_FRONTEND=noninteractive
so that prompts are automatically accepted during cloud-init run (Thanks @DavidBennettUK)
Change: Default ubuntu container version updated 16.04
=> 20.04
Feature: Update README.md
Twelfth Night
Change: Updated to Terraform 0.12/HCL2. This is a Breaking change
For Terraform 0.11. Pin module version to ~> v4.0
Change: The Tags 'Name', 'Environment' and 'Region' are no longer automatically created, populated and applied to the autoscaling group. This change is due to a combination of:
- Difficult to port old behaviour to Terraform 12
- It wasn't a great idea to pre-determine tags for users
- Since this release is a breaking change anyway, it's a good opportunity to change this.
The tags given in var.tags are rendered to the Autoscaling group as before
On Target
Feature: Added variable ${route53_fqdn}
(default ""
to preserve module historic behaviour by default). If creating a public DNS entry with this module then you may override the default constructed DNS entry by supplying a fully qualified domain name here.
Feature: Added output target group arn. - Thanks Kevin Green
Closer than close
4.8
Change: Added variable ${var.service_name}
(default "bastion-service
" to preserve module historic behaviour by default). Set this to a different value to avoid resource name collision when deploying more than one service using this module per vpc.
Change: Removed module version number and empty outputs from examples/full-with-public-ip