v4.1.0

4.1.0 (2023-11-16)

Features

• reserved IPs are now named using the service name, subnet zone and region where as previously there were always assigned a random name (#437) (32dc9bd)

NOTE: During an upgrade to this version the following update in place changes may be present in terraform plan

  # module.vpes.ibm_is_subnet_reserved_ip.ip["vpe-vpc-instance-subnet-c-postgresql-gateway-3-ip"] will be updated in-place
  ~ resource "ibm_is_subnet_reserved_ip" "ip" {
        id              = "0737-f3c78bfa-c8d8-4c45-bead-7e74a738224c/0737-c211fbb2-f63a-447c-a607-7907c0d17e97"
      ~ name            = "boneset-starboard-headsman-bonelet" -> "vpe-vpc-instance-postgresql-3"
        # (11 unchanged attributes hidden)
    }

Due to a known IBM terraform provider bug, a subsequent deploy might also show:

Changes to Outputs:
  ~ vpe_ips = {
      ~ vpe-vpc-instance-postgresql           = [
          ~ {
                id            = "0717-58a27750-f8b1-4972-a3ed-f47b29cdf693"
              ~ name          = "baton-numeral-chive-ducking" -> "vpe-vpc-instance-postgresql-1"
                # (2 unchanged attributes hidden)
            },
          ~ {
                id            = "0727-55bc587c-5f3e-4295-a41a-60187681af08"
              ~ name          = "circular-saucy-settling-persecute" -> "vpe-vpc-instance-postgresql-2"
                # (2 unchanged attributes hidden)
            },
          ~ {
                id            = "0737-c211fbb2-f63a-447c-a607-7907c0d17e97"
              ~ name          = "boneset-starboard-headsman-bonelet" -> "vpe-vpc-instance-postgresql-3"
                # (2 unchanged attributes hidden)
            },
        ]

If you run terraform apply -refresh-only after initial apply, it should update terraform state so no further changes show in subsequent plans.

v4.0.1

4.0.1 (2023-11-13)

Bug Fixes

• make cloud_services optional (#442) (8c53528)

v4.0.0

4.0.0 (2023-11-07)

Features

• Introduce allow dns resolution binding (#429) (a6b7a5f)

BREAKING CHANGES

• Some changes in the interface of this module as part of the introduction of DNS resolution binding:
  • Fixing Internal Inconsistencies: the method of passing VPE details for multi-tenant and single-tenant VPEs was standardized. The cloud_services and cloud_service_by_crn variables now follow the same type and naming conventions.
  • Removal of vpe_names variable: this variable was replaced with the vpe_name field in the cloud_services and cloud_service_by_crn.

❗While the interface of the module changes with this update, there will be no deletion or update of existing resources when upgrading to this new version, provided coherent parameters are passed as input. As example of update to make in your code, you may find interesting to see the updates made to the default and every-mt-vpe examples bundled in the module.

v3.2.0

3.2.0 (2023-11-03)

Features

• List of available service endpoints expanded

Bug fixes

• Some invalid service endpoints have been fixed or removed (#409) (195db64)

v3.1.0

3.1.0 (2023-10-10)

Features

• update terraform version constraints to >= 1.3.0, <1.6.0 (#414) (baa9614)

v3.0.0

3.0.0 (2023-09-22)

Bug Fixes

• remove invalid multi-tenant VPE references (#393) (a17b643)

BREAKING CHANGES

• Upon apply all existing VPE created in previous version of this module will be deleted and immediately re-created, which may result in a network termination. The IP of the VPE may change as part of this process.

v2.7.2

2.7.2 (2023-09-19)

Bug Fixes

• update module documentation (#389) (77f786d)

v2.7.1

2.7.1 (2023-09-04)

Bug Fixes

• fixed issue where the vpe_ips output may not contain any IPs (#372) (3800ae1)

v2.7.0

2.7.0 (2023-08-15)

Features

• add functionality to pass a custom name for the vpe gateway (#362) (3bf013b)

v2.6.0

2.6.0 (2023-08-04)

Features

• update to the data structure of the vpe_ips output. Added the gateway name as the key for each list of objects. This will help in differentiating the IPs for each gateways.(#354) (f864fbb).
  For example:
  • In previous versions, the output was in this format:

  [
     [
         {
             address       = "10.10.10.5"
             id            = "xxxx-xxxxx-xxxxxx-xxxxx"
             name          = "sandbank-disports-sleeve-dugout"
             resource_type = "subnet_reserved_ip"
             subnet        = ""
          },
         {
             address       = "10.20.10.5"
             id            = "xxxx-xxxxx-xxxxxx-xxxxx"
             name          = "bannister-food-quarrel-concept"
             resource_type = "subnet_reserved_ip"
             subnet        = ""
          },
      ],
     [
         {
             address       = "10.10.10.4"
             id            = "xxxx-xxxxx-xxxxxx-xxxxx"
             name          = "haunt-tank-recital-princess"
             resource_type = "subnet_reserved_ip"
             subnet        = ""
          },
         {
             address       = "10.20.10.6"
             id            = "xxxx-xxxxx-xxxxxx-xxxxx"
             name          = "vigorous-tarantula-cash-reverse"
             resource_type = "subnet_reserved_ip"
             subnet        = ""
          },
      ],
  ]
  

  • In v2.6.0, the output is now in the following format:

  {
      test-vpc-instance-account-management      = [
          {
              address       = "10.30.10.5"
              id            = "xxxx-xxxxx-xxxxxx-xxxxx"
              name          = "handwoven-poem-retention-mantis"
              resource_type = "subnet_reserved_ip"
              subnet        = ""
           },
          {
              address       = "10.10.10.12"
              id            = "xxxx-xxxxx-xxxxxx-xxxxx"
              name          = "smog-dastardly-bountiful-calf"
              resource_type = "subnet_reserved_ip"
              subnet        = ""
           },
       ]
      test-vpc-instance-billing                 = [
          {
              address       = "10.10.10.16"
              id            = "xxxx-xxxxx-xxxxxx-xxxxx"
              name          = "daffy-outfield-scrambled-showy"
              resource_type = "subnet_reserved_ip"
              subnet        = ""
           },
          {
              address       = "10.20.10.22"
              id            = "xxxx-xxxxx-xxxxxx-xxxxx"
              name          = "frogman-deflector-foe-deem"
              resource_type = "subnet_reserved_ip"
              subnet        = ""
           },
       ],
  }