Skip to content

Releases: terraform-ibm-modules/terraform-ibm-landing-zone-vpc

v7.7.0

13 Oct 13:51
v7.7.0
33d2c73
Compare
Choose a tag to compare

7.7.0 (2023-10-13)

Features

v7.6.0

09 Oct 15:36
badc1e8
Compare
Choose a tag to compare

7.6.0 (2023-10-09)

Features

  • updated required terraform version range to >= 1.3.0, <1.6.0 (#637) (badc1e8)

v7.5.0

13 Sep 15:30
v7.5.0
753b89d
Compare
Choose a tag to compare

7.5.0 (2023-09-13)

Updates (#621) (753b89d)

IBM Cloud Terraform provider v1.56.0 has added a new option for the "ibm_is_vpc" resource that will cause the default VPC ACL and Security Group to contain no rules (empty).

This release will retire the usage of existing backend scripts to remove all rules from the VPC default ACL and SG, and instead use this new provider option to accomplish the same feature.

Input variable changes:
The new provider option covers both security group and ACL in one variable, so we will be deprecating the individual "clean_" variables and replace them with a new single boolean to enable the feature.

  • REMOVED: clean_default_security_group and clean_default_acl
  • ADDED: clean_default_sg_acl, if set to "true" will trigger new VPC option to have empty default groups (default is "false")
  • CHANGED: security_group_rules now has a default of empty, instead of a broad default inbound rule that may not be desired
  • Validation has been added to make sure that clean_default_sg_acl has not been set to "true" while having rules specified in the security_group_rules input, which are in direct conflict with each other

Upgrade Notes:

If you have already deployed module with the "clean_" variables not specified, you should see no difference after upgrade.

If you have already deployed module with "clean_" variables set to "true/false", you will get an error after upgrade due to those variables being removed, and you should set the new clean_default_sg_acl variable instead. During a plan phase after upgrading, you may see the following resources marked for DESTROY, this is expected as these are the retired scripts that handled this feature in the past, and have been removed:

module.slz_vpc.null_resource.clean_default_acl[0] will be destroyed
module.slz_vpc.null_resource.clean_default_security_group[0] will be destroyed

v7.4.2

25 Aug 14:08
v7.4.2
51856ff
Compare
Choose a tag to compare

7.4.2 (2023-08-25)

Bug Fixes

  • add fix to support passing null for the prefix input variable (#605) (51856ff)

v7.4.1

09 Aug 15:25
v7.4.1
8707703
Compare
Choose a tag to compare

7.4.1 (2023-08-09)

Bug Fixes

v7.4.0

26 Jul 15:46
v7.4.0
518204d
Compare
Choose a tag to compare

7.4.0 (2023-07-26)

Features

  • subnet CRN now added to the subnet_detail_list output (#587) (518204d)

v7.3.2

10 Jul 14:26
v7.3.2
2f74af0
Compare
Choose a tag to compare

7.3.2 (2023-07-10)

Bug Fixes

  • Acls created for network cidr are open to Any IP (#569) (2f74af0)

v7.3.1

19 Jun 13:22
v7.3.1
6b18801
Compare
Choose a tag to compare

7.3.1 (2023-06-19)

Bug Fixes

  • update modules references to point to hashicorp module registry (6b18801)

v7.3.0

14 Jun 05:02
6718c01
Compare
Choose a tag to compare

7.3.0 (2023-06-14)

Features (#542) (6718c01)

  • Added the ability to to pass multiple network CIDRs to the module. This feature means the input variable network_cidr has been renamed to network_cidrs and changed from a string to a list type. If you are updating to this version of the module from a previous version, you now need to change the way you pass values to this variable. For example:

    • Versions < 7.3.0: network_cidr = "10.0.0.0/8"
    • Versions >= 7.3.0: network_cidrs = ["10.0.0.0/8"]

v7.2.0

18 May 15:12
3194ff7
Compare
Choose a tag to compare

7.2.0 (2023-05-18)

Features