v4.8.4

4.8.4 (2024-03-09)

Bug Fixes

• deps: update terraform ibm to latest for the deployable architecture solution (#425) (803a7a4)

v4.8.3

4.8.3 (2024-03-02)

Bug Fixes

• deps: update terraform-module (#422) (bcef67b)

v4.8.2

4.8.2 (2024-02-29)

Bug Fixes

• resource_group_id is only required if creating KP instance (#421) (6cfc5fa)

v4.8.1

4.8.1 (2024-02-28)

Bug Fixes

• Update DA to claim from "CIS IBM Cloud Foundations Benchmark" profile (#420) (ca3a356)

v4.8.0

4.8.0 (2024-02-28)

Features

• Created DA solution (#418) (e60edb5)

v4.7.1

4.7.1 (2024-02-27)

Bug Fixes

• extend the required terraform version to < 1.7 (#416) (c366731)

v4.7.0

4.7.0 (2024-02-23)

Features

• key_protect_endpoint_type variable has been renamed to key_protect_allowed_network and only supports the following values: public-and-private (default value) and private-only (#413) (5841fb0)

v4.6.0

4.6.0 (2024-02-01)

Features

• added kp_private_endpoint and kp_public_endpoint outputs (#404) (258bda5)
• updated Key Protect module to version v2.5.1. This version will cause an expected update in place on the Key Protect instance if you have one provisioned. See v2.5.1 release notes for details. (#404) (258bda5)

v4.5.0

4.5.0 (2024-01-31)

Features (#400) (0148340)

• The following variables have been removed force_delete, force_delete_key_ring, existing_key_map, as its now possible to pass them as part of a new input variable list called keys. This has replaced the old variables key_map and existing_key_map as it supports creating key in existing and new key rings using a boolean. See updated usage on how to consume module.
  Current infrastructure will not be impacted when updating to this version if migration to new usage is done correctly. For example:

  In previous versions:

  key_map = {
    "key-ring-name-1" = ["key-1", "key-2"]
  }
  
  existing_key_map = {
    "key-ring-name-2" = ["key-3", "key-4"]
  }

  In this version:

  keys = [
    {
      key_ring_name = "key-ring-name-1"
      keys = [
        {
          key_name = "key-1"
        },
        {
          key_name = "key-2"
        }
      ]
    },
    {
      key_ring_name = "key-ring-name-2"
      existing_key_ring = true
      keys = [
        {
          key_name = "key-3"
        },
        {
          key_name = "key-4"
        }
      ]
    }
  ]

  In addition, the output of the module has changed to now only have one "keys" output. below is an example of how the output has changed:

  Older versions:

  module.kms_all_inclusive.keys["key-ring-name-1.key-1"]
  module.kms_all_inclusive.keys["key-ring-name-1.key-2"]
  module.kms_all_inclusive.existing_key_ring_keys["existing-key-ring.key-3"]
  module.kms_all_inclusive.existing_key_ring_keys["existing-key-ring.key-4"]
  module.kms_all_inclusive.key_protect_guid

  This version:

  module.kms_all_inclusive.keys["key-ring-name-1.key-1"]
  module.kms_all_inclusive.keys["key-ring-name-1.key-2"]
  module.kms_all_inclusive.keys["existing-key-ring.key-3"]
  module.kms_all_inclusive.keys["existing-key-ring.key-4"]
  module.kms_all_inclusive.kms_guid

v4.4.2

4.4.2 (2023-11-27)

Bug Fixes

• deps: update terraform-module (#371) (e1489e9)