v2.0.7

2.0.7 (2024-03-01)

Bug Fixes

• required permissions for Event Streams solution (#200) (9cd29dd)

v2.0.6

2.0.6 (2024-02-28)

Bug Fixes

• fix architecture diagram link for catalog offering (#199) (dd49732)

v2.0.5

2.0.5 (2024-02-27)

Bug Fixes

• extend the required terraform version to < 1.7 (#198) (eb0f9eb)

v2.0.4

2.0.4 (2024-02-26)

Bug Fixes

• onboard event streams DA to catalog (#193) (8ead10d)

v2.0.3

2.0.3 (2024-02-24)

Bug Fixes

• deps: update terraform terraform-ibm-modules/cbr/ibm to v1.19.0 (#194) (5f6dbfe)

v2.0.2

2.0.2 (2024-02-21)

Bug Fixes

• updated required IBM provider version constraint of fscloud submodule to >= 1.56.1, < 2.0.0 (#184) (6e08fd7)

v2.0.1

2.0.1 (2024-02-17)

Bug Fixes

• deps: update terraform terraform-ibm-modules/cbr/ibm to v1.18.1 (#190) (1b64550)

v2.0.0

2.0.0 (2024-02-13)

Updates (#178) (f665852)

• Support for managing the service to service KMS authorization policy has been removed from this module. For more infomation on why, see About KMS encryption. This now means that the auth policy must be in place before you attempt to provision an Event Streams instance with KMS encryption enabled.
  • Due to this change, the following variables have bee removed skip_iam_authorization_policy, existing_kms_instance_guid, and kms_encryption_enabled. If you wish to enable KMS encryption, just pass a value for the kms_key_crn input variable.

BREAKING CHANGES

• If updating to this version from a previous version, and if you were using the module to manage the KMS auth policy, you will see the auth policy as identified for destroy. In order to ensure there is no interruption to service when updating, it is recommended that you create a global auth policy (outside of this terraform state) to allow all Event Stream instances in your account read access to the KMS service you are using before you proceed with upgrade. Once your upgrade is complete, and terraform has destroyed the old auth policy, you may wish to create a new instance-to-instance scoped policy if you wish to remove the globally scoped one. It is important not to create the policy with Terraform if it shares the same state as this module. Refer to About KMS encryption for more details.

UPDATE (11th Oct 2024):

The Event Streams service was updated to allow the ability to now manage a KMS key in the same state as the Event Streams instance. So support to create the KMS auth policy has been added back in v2.4.0

v1.4.16

1.4.16 (2024-01-27)

Bug Fixes

• deps: update terraform terraform-ibm-modules/cbr/ibm to v1.18.0 (#174) (4fe314e)

v1.4.15

1.4.15 (2024-01-03)

Bug Fixes

• moved fscloud submodule profile from profiles/fscloud -> modules/fscloud as per hashicorp standards (#165) (76e83ff)