Releases: FairwindsOps/terraform-bastion
Releases · FairwindsOps/terraform-bastion
gcp-v1.1.1: adds support for google terraform provider 4.27.x+
Correct iam.tf project variable type (#74)
gcp-v1.0.2: Fix gcp iam resource
Fix storage bucket IAM resource (#72) Fixing a mistake in the stoage bucket iam resource.
gcp-v1.0.1: Update to support google terraform provider 4.x (#71)
Adds project variable to necessary iam resources to add support google tf provider 4.x+
gcp-v1.0.0
- Introducting a breaking change by updating the terraform required_providers block to the format supported for terraform versions >=0.13
aws-v3.0.0
- Introducting a breaking change by updating the terraform required_providers block to the format supported for terraform versions >=0.13
- Make
ssh_public_key_file
optional
aws-v2.1.0
aws-v2.1.0
- Add input to encrypt the root volume (true by default).
gcp-v0.1.3
- Update startup-script so that the upgrade command runs as an
at
. This is a bugfix in the situation that it upgradegoogle-guest-agent
which would restart the startup-script and DNS Update + user creation will never happen.
aws-v2.0.1
- Update startup-script so that the upgrade command runs as an
at
. This is a bugfix in the situation that it upgrades a package that could restart the startup-script and DNS Update + user creation will never happen.
aws-v2.0.0
aws-v2.0.0
- Revert the previous change to
associate_public_ip_address
as there were unintended consequences with the default value.
aws-v1.0.0
aws-v1.0.0
- Remove
associate_public_ip_address
argument; this is a potentially backwards-incompatible change that will cause public IP address allocation for the host to be determined based on the subnet in which the bastion host is launched. To ensure bastion hosts still receive public IP addresses, make sure they are launched within a public subnet.