Skip to content

Releases: FairwindsOps/terraform-bastion

gcp-v1.1.1: adds support for google terraform provider 4.27.x+

08 Jul 18:55
f4989ba
Compare
Choose a tag to compare
Correct iam.tf project variable type (#74)

gcp-v1.0.2: Fix gcp iam resource

07 Jul 15:02
69e5d6c
Compare
Choose a tag to compare
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)

01 Jul 21:32
14b7e65
Compare
Choose a tag to compare

Adds project variable to necessary iam resources to add support google tf provider 4.x+

gcp-v1.0.0

11 Jan 19:50
7544cd2
Compare
Choose a tag to compare
  • Introducting a breaking change by updating the terraform required_providers block to the format supported for terraform versions >=0.13

aws-v3.0.0

11 Jan 19:48
7544cd2
Compare
Choose a tag to compare
  • 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

26 Jun 02:00
784948c
Compare
Choose a tag to compare

aws-v2.1.0

  • Add input to encrypt the root volume (true by default).

gcp-v0.1.3

21 May 18:33
6c224da
Compare
Choose a tag to compare
  • Update startup-script so that the upgrade command runs as an at. This is a bugfix in the situation that it upgrade google-guest-agent which would restart the startup-script and DNS Update + user creation will never happen.

aws-v2.0.1

21 May 18:33
6c224da
Compare
Choose a tag to compare
  • 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

17 Mar 12:42
Compare
Choose a tag to compare

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

11 Mar 21:50
32b3bf4
Compare
Choose a tag to compare

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.