v7.13.0

7.13.0 (2023-11-24)

Features

• cleanup, updated variables and basic example (#670) (b1a38d0)

v7.12.0

7.12.0 (2023-11-20)

Features

• added support to create resources in existing VPC and use existing subnets. See Existing VPC and subnets Example (#638) (f0c5b08)

v7.11.0

7.11.0 (2023-11-13)

Features

• surface additional hub-spoke dns sharing outputs (#668) (4228427)

v7.10.0

7.10.0 (2023-11-10)

Features

• introduce support for manual resolver resolver (#663) (13b7d08)
• introduce hub-spoke examples (using manual and delegated resolver)

v7.9.0

7.9.0 (2023-11-08)

Features

• expose hub vpc inputs (#662) (1c15668)

v7.8.0

7.8.0 (2023-11-07)

Features

• expose enable_hub variable (#661) (c659a93)

v7.7.0

7.7.0 (2023-10-13)

Features

• added new vpc_data output (#641) (33d2c73)

v7.6.0

7.6.0 (2023-10-09)

Features

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

v7.5.0

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

7.4.2 (2023-08-25)

Bug Fixes

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