Releases: mesoform/terraform-infrastructure-modules
Secure Swarm blue/green deployment impovements
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
Added CloudSQL composite module for private PostgreSQL resources (instance, databases and users)
Fix regional_update_policy usage
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
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
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
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
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
- Local variable used for setting
-
Stateless MIG deployments are now possible by setting
stateful_instance_group=false
. Thestateful_disk
block for the persistent disk is now dynamic, with the stateful disk being configured if bothstateful_instance_group
andpersistent_disk
are true. -
Updated documentation
-
BREAKING: Updated the format of both the
access_config
and thenetwork_ip
variables to remove references tozone
. 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
Persistent data disk can be omitted from secure-swarm deployment by setting persistent_disk=false
Fix mismatch between blue and green instance template
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
Merge pull request #82 from mesoform/bug/pk2m-255/disk-size-default pk2m-255 Ability to specify boot disk size