v4.5.2

4.5.2 (2023-08-21)

⚠️ This release will currently not deploy in IBM Schematics due to a known provider bug. Please use v4.5.3 which has the fix for this if running in IBM Schematics.

Bug Fixes

• update to landing-zone-vsi v2.5.0 (#535) (c91b619)

⚠️ Warning

If you are upgrading from a previous release, and you are using the override JSON to provision additional VSI data volumes using the block_storage_volumes value, the terraform plan will tell you that it wants to destroy the volumes that are in the Default resource group and recreate them in the same resource group that the VSIs are provisioned in.

If indeed you wish to continue to keep your data volumes in the Default resource group (to prevent them from being destroyed and recreated on upgrade), you can achieve this by adding the Default resource group ID into the block_storage_volumes array in the vsi part of the override JSON. For example:

{
.....
  "vsi": [
    {
        "boot_volume_encryption_key_name": "PREFIX-vsi-volume-key",
        "image_name": "ibm-redhat-8-6-minimal-amd64-5",
        "machine_type": "cx2-8x16",
        "name": "sbx-workload",
        "resource_group": "PREFIX-workload-rg",
        "block_storage_volumes": [
            {
                "name":           "datavol",
                "profile":        "general-purpose",
                "capacity":       100,
                "encryption_key": "PREFIX-vsi-volume-key",
                "resource_group_id" : "65xxxxxxxxxxxxxxxa3fd"
            }
        ]
....
    }
  ]
....
}