Releases: terraform-ibm-modules/terraform-ibm-landing-zone-vsi
Releases · terraform-ibm-modules/terraform-ibm-landing-zone-vsi
v2.6.0
v2.5.0
2.5.0 (2023-08-18)
Features
- added the ability to optionally specify resource group in the
block_storage_volumes
variable. If not specified, it will use the value of theresource_group_id
variable. Previously it was defaulting to the Default resource group. (#507) (9ea08ab)
⚠️ Warning
If you are upgrading from a previous release, and your config was set up to deploy a VSI with additional data volumes using the block_storage_volumes
variable, 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 correct group (either the group defined in the required resource_group_id
variable, or the group defined in the block_storage_volumes
variable itself).
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
variable. For example:
block_storage_volumes = [
{
name = "my-data-vol"
profile = "10iops-tier"
resource_group_id = "65xxxxxxxxxxxxxxxa3fd" # This should be the ID of the Default resource group in your account
}]
v2.4.4
v2.4.3
v2.4.2
v2.4.1
v2.4.0
2.4.0 (2023-07-21)
Features
- deps: updated required provider version to
>= 1.54.0
in order to pull in provider fix for auth policy issue (#490) (e41a3de)
v2.3.2
v2.3.1
v2.3.0
2.3.0 (2023-06-09)
Features ((#467) (8f10810)
- added new variable
kms_encryption_enabled
which now needs to be set totrue
to enable KMS encryption - added support to create KMS auth policy along with variable
skip_iam_authorization_policy
to toggle policy creation on or off - added extra validation around the use of KMS variables
- added a new FSCloud profile terraform submodule (see
profiles/fscloud
) and an example on how to use it (seeexamples/fscloud
)