v0.9.0

Terraform 1.0 upgrade: We have verified that this repo is compatible with Terraform 1.0.x!

• From this release onward, we will only be running tests with Terraform 1.0.x against this repo, so we recommend updating to 1.0.x soon!
• To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above.
• Once all Gruntwork repos have been upgrade to work with 1.0.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.

v0.8.2

Description

• Add Ubuntu image + remove gcloud update from CircleCI config
• Replace gofmt with goimports
• Implement Terraform validate test

Related links

• #69
• #70
• #71

v0.8.1

Modules affected

• vpc-network

Description

This release migrates the use of Terraform list() in the vpc-network module to tolist() in order to be compatible with future versions of Terraform.

Related links

• #65

v0.8.0

Modules affected

• bastion-host
• network-firewall
• network-peering
• project-host-configuration
• vpc-network

Description

• Terraform 0.14 upgrade: We have verified that this repo is compatible with Terraform 0.14.x!
  • From this release onward, we will only be running tests with Terraform 0.14.x against this repo, so we recommend updating to 0.14.x soon!
  • To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.14.x.
  • Once all Gruntwork repos have been upgrade to work with 0.14.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.

Related links

• #68

v0.7.1

Modules affected

• network-firewall
• vpc-network

Description

This release adds two new variables: var.public_services_secondary_cidr_block and var.private_services_secondary_cidr_block that allow the public and private services secondary IP CIDR ranges to be specified manually. It is intended for backwards compatibility with existing GKE clusters to prevent changing the automatically assigned subnetwork IP ranges and recreating the clusters. Please see the migration guide in the GKE module if your upgrading to this release as it will cause existing clusters to be recreated. It also adds the new secondary IP range to the private inbound compute firewall.

Related links

• #67

v0.7.0

Modules affected

• vpc-network [BACKWARDS INCOMPATIBLE]

Description

This release fixes a GKE cluster creation issue (see gruntwork-io/terraform-google-gke#118) due to a change in Google's APIs that prevents the pod secondary range name having the same name as the services secondary range name. We set defaults for the new secondary range names, however we use variables to allow backwards compatibility with existing GKE clusters. Please see the migration guide in the GKE module if your upgrading this release as it will cause existing clusters to be recreated.

Special thanks

Special thanks to @brianpham for their contributions!

Related links

• #64

v0.6.0

Modules affected

• (none)

Description

• Terraform 0.13 upgrade: We have verified that this repo is compatible with Terraform 0.13.x!
  • From this release onward, we will only be running tests with Terraform 0.13.x against this repo, so we recommend updating to 0.13.x soon!
  • To give you more time to upgrade, for the time being, all modules will still support Terraform 0.12.26 and above, as that version has several features in it (required_providers with source URLs) that make it more forwards compatible with 0.13.x.
  • Once all Gruntwork repos have been upgrade to work with 0.13.x, we will publish a migration guide with a version compatibility table and announce it all via the Gruntwork Newsletter.

Related links

• #58

v0.5.0

Modules affected

• vpc-network [BACKWARDS INCOMPATIBLE]

Description

This release reverses a breaking change made in v0.3.0 that switched the VPC NAT routing by referencing the private subnetwork instead of the public one. With this change resources on the private subnetwork will no longer have outbound internet access unless they are assigned an external IP address.

Related links

• #57

v0.4.0

Modules affected

• vpc-network [BACKWARDS INCOMPATIBLE]

Description

This release replaces the deprecated enable_flow_logs parameter from the vpc-network module in favor of the new log_config parameter. log_config supports specific additional parameters such as aggregation_internal, flow_sampling and metadata.

Migration Guide

You should remove all references to the enable_flow_logs parameter when using the vpc-network module and instead replace it with log_config. Existing networks should set log_config to the default parameters or customize them based on your needs:

log_config = {
  aggregation_interval = "INTERVAL_10_MIN"
  flow_sampling        = 0.5
  metadata             = "INCLUDE_ALL_METADATA"
}

Special thanks

Special thanks to @craigedmunds and @0hlov3 for their contributions!

Related links

• #47
• #51
• #54

v0.3.0

Modules affected

• vpc-network [BACKWARDS INCOMPATIBLE]

Description

This release fixes a configuration problem with the VPC NAT routing by referencing the private subnetwork instead of the public one. In theory resources on the public subnetwork should still have outbound internet connectivity, but we are still marking this as a backwards incompatible release.

Special thanks

Special thanks to @AkhilGNair for their contribution!

Related links

• #53