Releases: FairwindsOps/terraform-bastion
Releases · FairwindsOps/terraform-bastion
0.3.3
0.3.2
v0.3.1
v0.3.0
Added
- An
additional_users
input creates SSH users on the bastion. The available per-user fields are login, gecos (full name), shell, supplemental groups, and SSH authorized_keys. - An
additional_user-data
input adds content toward the end of EC2 User Data. The additional User Data is executed before users specified inadditional_users
are added.
Changed
- The Auto Scaling Group (and its bastion EC2) will now be recreated when there is an update to the Launch Configuration. The new Auto Scaling Group will be created before the current one is deleted. Previously the EC2 remained untouched after a Launch Configuration update, which left its recycling to operator discretion.
Fixed
- The Launch Configuration lifecycle block incorrectly specified ignoring
image_id
, and a new AMI caused an update to the Launch Configuration. A new AMI will now be ignored. Recycling the EC2 due to a new AMI should be less necessary as this module enables automatic Ubuntu updates.
v0.2.0
Changed
- The
bastion_name
module input is now used as the hostname for DNS registration, instead ofbastion
. After runningterraform apply
and updating SSH configurations to use the new hostname, please manually remove the Route53 record namedbastion
.
Fixed
- The Route53 zone ID is now used by the DNS registration script instead of the zone name. This is more explicit, and handles cases where multiple (public and private) zones exist with the same name.
v0.1.1
Added
- A new
remove_root_access
input to remove sudo access from the ubuntu user. This defaults to being enabled, to disable it defineremove_root_access = "false"
.
Fixed
- The instructions for modifying ssh_config files to use the bastion are now more complete.