v4.4.0

4.4.0 (2024-11-28)

Features

• In this release, you can have more than 1 vsi per subnet when using secondary VNIs.

UPGRADE NOTES: When updating from v4.3.x to this version, if you have a secondary VNI and floating IPs for the secondary VNI enabled enabled, these resources will be recreated. There will be no effect on the VSI. In case, you need to prevent recreation of the secondary VNI and floating IPs associated with the secondary VNI, use the following terraform move commands based on the environment you are running the terraform module.
Terraform CLI:

terraform state mv 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["<region>-1"]' 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["<zone-1-subnet-name>-0"]'
terraform state mv 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["<region>-2"]' 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["<zone-2-subnet-name>-0"]'
terraform state mv 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["<region>-3"]' 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["<zone-3-subnet-name>-0"]'
terraform state mv 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-1-subnet-name>"]' 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-1-subnet-name>-0"]'
terraform state mv 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-2-subnet-name>"]' 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-2-subnet-name>-0"]'
terraform state mv 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-3-subnet-name>"]' 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-3-subnet-name>-0"]'

Schematics:

ibmcloud schematics workspace state mv --id <WORKSPACE_ID> --source 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["us-south-1"]' --destination 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["<zone-1-subnet-name>-0"]'
ibmcloud schematics workspace state mv --id <WORKSPACE_ID> --source 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["us-south-2"]' --destination 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["<zone-2-subnet-name>-0"]'
ibmcloud schematics workspace state mv --id <WORKSPACE_ID> --source 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["us-south-3"]' --destination 'module.<module-name>.ibm_is_virtual_network_interface.secondary_vni["<zone-3-subnet-name>-0"]'
ibmcloud schematics workspace state mv --id <WORKSPACE_ID> --source 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-1-subnet-name>"]' --destination 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-1-subnet-name>-0"]'
ibmcloud schematics workspace state mv --id <WORKSPACE_ID> --source 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-2-subnet-name>"]' --destination 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-2-subnet-name>-0"]'
ibmcloud schematics workspace state mv --id <WORKSPACE_ID> --source 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-3-subnet-name>"]' --destination 'module.<module-name>.ibm_is_floating_ip.vni_secondary_fip["<zone-3-subnet-name>-0"]'

(#753) (5e39a48)