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.