v3.3.0

In this release

• remove extra readers in gcs-to-bq-with-dataflow example (issue: 128)
• make VPC creation optional in net-vpc module to allow managing a pre-existing VPC
• make HA VPN gateway creation optional in net-vpn-ha module
• add retention_policy in gcs module
• refactor net-address module variables, and add support for internal address purpose

v3.2.0

In this release

• incompatible change add alias IP support in cloud-vm module
• add tests for data-solutions examples
• fix apply errors on dynamic resources in dataflow example
• make zone creation optional in dns module
• new quota-monitoring end-to-end example in cloud-operations

v3.1.1

This release is a bugfix in the project module.

v3.1.0

This release adds support for specifying a different project id for the peering configuration in the GKE module. It's an incompatible change, since peering_config.project_id now needs to be set when using peering_config, a null value is acceptable and will fallback to the previous behaviour of using the project_id variable for the peering.

v3.0.0

In this release

• incompatible change the top-level infrastructure folder has been renamed to networking
• add end-to-end example for ILB as next hop
• add basic tests for foundations and networking end-to-end examples
• fix Shared VPC end-to-end example and documentation

v2.8.0

In this release

• new end-to-end example on DNS granular IAM via Service Directory
• add missing dependency on IAM roles to feed id output in pubsub module

v2.7.1

In this release

• fix provider issue in bigquery module

v2.7.0

In this release

• add support for VPC connector and ingress settings to cloud-function module
• add support for logging to net-cloudnat module

v2.6.0

In this release

• incompatible change setting zone in the compute-vm module is now done via an optional zones variable, that accepts a list of zones
• fix optional IAM permissions in folder unit module

v2.5.0

In this release

• new vpc-sc module
• add support for Shared VPC to the project module
• fix bug with compute-vm address reservations introduced in [2.4.1]