Releases: terraform-ibm-modules/terraform-ibm-landing-zone
Releases · terraform-ibm-modules/terraform-ibm-landing-zone
v6.0.1
v6.0.0
6.0.0 (2024-09-20)
Updates (#870) (693c8e2)
- updated landing-zone-vsi module to
4.2.0- In previous versions, it was found that adding or removing VSIs after they have been initially created by this module can cause VSIs to be destroyed and recreated due to the naming convention and logic being used. In order to fix this, the naming convention has changed in v4 of the module to be
prefix- + the last 4 digits of the subnet ID + a sequential number for each subnet. For example,prefix-3ad7-001.
- In previous versions, it was found that adding or removing VSIs after they have been initially created by this module can cause VSIs to be destroyed and recreated due to the naming convention and logic being used. In order to fix this, the naming convention has changed in v4 of the module to be
- Refactored the logic used to create OCP clusters. Its now using the base-ocp-vpc module
- This module has some extra functionality which requires the runtime to have access to IBM Cloud private endpoints.
BREAKING CHANGES
- If you were to upgrade the 'Red Hat OpenShift Container Platform on VPC landing zone' solution, or the 'VSI on VPC landing zone' from a previous version to this version, infrastructure will be destroyed and recreated. To prevent this, you should upgrade directly to version
6.8.1which handles migration when upgrading the DA in projects.
v5.33.0
v5.32.0
v5.31.3
v5.31.2
v5.31.1
v5.31.0
v5.30.1
v5.30.0
5.30.0 (2024-08-27)
Features
- added support to the root level module
cosinput variable to configuremanagement_events(true or false) in theactivity_trackingconfiguration. The root level required IBM provider version constrains have been updated to>= 1.67.0, < 2.0.0since this feature was only added in1.67.0.(#847) (835d676)