Skip to content

Releases: mesoform/terraform-infrastructure-modules

Secure Swarm blue/green deployment impovements

05 Sep 08:58
c2f9eca
Compare
Choose a tag to compare

Prior releases did not have all Instance Template attributes in the blue_instance_template and green_instance_template variables.
All required attributes have been added to improve usage of blue/green deployments

CloudSQL composite module for private PostgreSQL

15 Aug 16:51
c0c0858
Compare
Choose a tag to compare

Added CloudSQL composite module for private PostgreSQL resources (instance, databases and users)

Fix regional_update_policy usage

28 Jul 10:12
2d67dd0
Compare
Choose a tag to compare

Update

Link to new MCP repositories for future versions of MCP Services and Foundational modules

Bug Fix

The Regional Instance Group Manager now uses the regional_update_policy variable, which contains some extra required values compared to update_policy which the resource previously used.

Fix secure swarm boot_device_name default name

06 May 10:45
d5bfd43
Compare
Choose a tag to compare

stateful_disk.device_name was hardcoded to ${local.name}-boot which did not match var.boot_device_name (default null) unless specified to do so.

Changed to use local.boot_device_name which defaults to "${local.name}-boot" if var.boot_device_name is null

Fix forced resource recreation

05 Apr 16:06
3170605
Compare
Choose a tag to compare

Fixes:

  • Make separate regional_update_policy variable for regional instance group managers to stop forced recreation existing zonal managed instance groups.
  • boot_device_name variable added to replace static value that was causing forced recreation of existing instance templates

Bug fix: Secure Swarm Node instance template description

30 Mar 08:56
c5a1b45
Compare
Choose a tag to compare

Bug fix: added instance_template_description variable, to avoid forced resource recreation after previous release had updated the value for the Instance Template's description

Regional Managed Instance Group

23 Mar 14:04
02e735b
Compare
Choose a tag to compare

Changes to secure-swarm-node module:

  • If the zone variable is not set, a regional MIG is deployed instead of the default zonal one.

    • Local variable used for setting local.name to either ${var.name} or ${var.name}-${var.zone} depending on type of deployment
  • Stateless MIG deployments are now possible by setting stateful_instance_group=false. The stateful_disk block for the persistent disk is now dynamic, with the stateful disk being configured if both stateful_instance_group and persistent_disk are true.

  • Updated documentation

  • BREAKING: Updated the format of both the access_config and the network_ip variables to remove references to zone. Previous configuration was too specific to zonal MIG deployments:

      access_config = {
        a = [{nat_ip = "35.0.0.2"}]
      }
      network_ip = {
        a = "10.0.0.2"
       } 

    The new configuration would be:

      access_config = [{nat_ip = "35.0.0.2"}]
      network_ip = "10.0.0.2"

    As the module would only be deploying to one zone anyway

Optional Persistent Disk

21 Mar 17:01
0b535c9
Compare
Choose a tag to compare

Persistent data disk can be omitted from secure-swarm deployment by setting persistent_disk=false

Fix mismatch between blue and green instance template

11 Jan 18:12
236844f
Compare
Choose a tag to compare
Merge pull request #83 from mesoform/bug/pk2m-255/disk-size-default

Update blue instance template to match green

Fix to allow specifying boot disk size

11 Jan 18:02
7cd1fd5
Compare
Choose a tag to compare
Merge pull request #82 from mesoform/bug/pk2m-255/disk-size-default

pk2m-255 Ability to specify boot disk size