v3.1.6

3.1.6 (2025-01-11)

Bug Fixes

• deps: update terraform terraform-ibm-modules/kms-all-inclusive/ibm to v4.19.2 (#368) (43b6158)

v3.1.5

3.1.5 (2025-01-11)

Bug Fixes

• deps: update terraform ibm to latest for deployable architectures (#366) (c2b69ad)

v3.1.4

3.1.4 (2024-12-21)

Bug Fixes

• deps: update terraform ibm to latest for deployable architectures (#360) (454593a)

v3.1.3

3.1.3 (2024-12-21)

Bug Fixes

• deps: update terraform terraform-ibm-modules/kms-all-inclusive/ibm to v4.19.1 (#363) (5ba4b3d)

v3.1.2

3.1.2 (2024-12-21)

Bug Fixes

• deps: update terraform terraform-ibm-modules/kms-all-inclusive/ibm to v4.19.0 (#362) (ff15606)

v3.1.1

3.1.1 (2024-12-20)

Bug Fixes

• deps: update terraform terraform-ibm-modules/kms-all-inclusive/ibm to v4.18.2 (#359) (b034237)

v3.1.0

3.1.0 (2024-12-18)

Features

• Root module updates:
  • existing_kms_instance_guid is no longer a supported input. The code will now parse the GUID from the KMS key CRN
  • added new input use_same_kms_key_for_backups to give more control over KMS key usage
  • kms_encryption_enabled has been renamed to use_ibm_owned_encryption_key
• fscloud submodule updates:
  • added new inputs use_default_backup_encryption_key and use_same_kms_key_for_backups
• DA updates
  • Removed the input existing_backup_kms_instance_crn. If you want to use a different KMS key for backups, you can use the existing_backup_kms_key_crn input to use an existing key. The DA only supports creating an new key that will be used for both data and backups encryption.
  • The skip_iam_authorization_policy input has been renamed to skip_es_kms_auth_policy
  • If passing a value for ibmcloud_kms_api_key, and creating a KMS auth policy, that policy will now be scoped to the exact KMS key.

(#351) (e7598e2)

v3.0.2

3.0.2 (2024-12-18)

Bug Fixes

• deps: update terraform ibm to latest for deployable architectures (#357) (349c80e)

v3.0.1

3.0.1 (2024-12-14)

Bug Fixes

• deps: update terraform ibm to latest for deployable architectures (#355) (ff35a97)

v3.0.0

3.0.0 (2024-12-11)

Features

• Support has been added for adding and removing a topic and quota at any index of the topics and quotas input variable lists. Previously, it was only possible to add or remove topics and quotas at the end of the list. (#350) (4bcbef5)

BREAKING CHANGES

• When upgrading from a previous version, if you configure topics, run the following Terraform move commands based on your environment to avoid recreating the topics:

  • Terraform CLI

    terraform state mv 'module.<module-name>.ibm_event_streams_topic.es_topic[<index of topic-name-1>]' 'module.<module-name>.ibm_event_streams_topic.es_topic["<topics-name-1>"]'
    ...

  • Schematics

    ibmcloud schematics workspace state mv --id <workspace-id> --source 'module.<module-name>.ibm_event_streams_topic.es_topic[<index of topic-name-1>]' --destination 'module.<module-name>.ibm_event_streams_topic.es_topic["<topic-name-1>"]'
    ...
    

• Similarly if you configure quotas, run the following commands:

  • Terraform CLI

    terraform state mv 'ibm_event_streams_quota.eventstreams_quotas[<index of quota-entity-1>]' 'ibm_event_streams_quota.eventstreams_quotas["<quota-entity-1>"]'
    ...

  • Schematics

    ibmcloud schematics workspace state mv --id <workspace-id> --source 'ibm_event_streams_quota.eventstreams_quotas[<index of quota-entity-1>]' --destination 'ibm_event_streams_quota.eventstreams_quotas["<quota-entity-1>"]'
    ...