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        = ""
           },
       ],
  }
  

v2.5.0

2.5.0 (2023-08-03)

Features

• updated list of supported services (#308) (a77b293)

v2.4.1

2.4.1 (2023-06-26)

Bug Fixes

• updated documentation and examples to use hashicorp registry syntax (#329) (6447906)

v2.4.0

2.4.0 (2023-06-07)

Features

• new outputs added: vpe_ips and crn (#323) (c3fdff5)

v2.3.1

2.3.1 (2023-05-29)

Bug Fixes

• Fix an issue preventing from creating VPE when the VPE name is unknown at plan time
• Fix an issue where reserved IPs were not created when cloud_service_by_crn was used

v2.3.0

2.3.0 (2023-05-22)

Features

• update required ibm provider version to >= 1.52.0 (#304) (e8aa6a1)