Skip to content

Releases: terraform-ibm-modules/terraform-ibm-cos

v6.12.0

19 Sep 11:53
v6.12.0
1dc4ce2

Choose a tag to compare

6.12.0 (2023-09-19)

Features

  • moved fscloud profile from profiles folder to modules folder (#440) (1dc4ce2)

v6.11.2

12 Sep 10:23
v6.11.2
d7bf2fb

Choose a tag to compare

6.11.2 (2023-09-12)

Bug Fixes

v6.11.1

06 Sep 15:11
v6.11.1
70aec00

Choose a tag to compare

6.11.1 (2023-09-06)

Bug Fixes

  • add a description to auth policy created by this module (#432) (70aec00)

v6.11.0

24 Aug 07:21
v6.11.0
ecc6ca6

Choose a tag to compare

6.11.0 (2023-08-24)

Features

  • update required ibm provider version to >= 1.56.1 (#428) (ecc6ca6)

v6.10.1

09 Aug 15:24
v6.10.1
62b27a8

Choose a tag to compare

6.10.1 (2023-08-09)

Bug Fixes

v6.10.0

11 Jul 14:51
v6.10.0
6288ad7

Choose a tag to compare

6.10.0 (2023-07-11)

Features

  • added a new buckets submodule which supports creating multiple buckets (#265) (6288ad7)

v6.9.0

30 Jun 11:37
v6.9.0
220e9c3

Choose a tag to compare

6.9.0 (2023-06-30)

Features

  • The default value of retention_enabled has changed from true to false. Any consumers who are upgrading to this version and want retention enabled must now explicitly set retention_enabled = true when consuming (#421) (220e9c3)

v6.8.0

24 Jun 08:55
7efbcbd

Choose a tag to compare

6.8.0 (2023-06-24)

Features

  • updated required ibm provider version constraint to >= 1.54.0, < 2.0.0 to pickup this fix (#420) (7efbcbd)

v6.7.0

19 Jun 10:04
v6.7.0
a8e5e2d

Choose a tag to compare

6.7.0 (2023-06-19)

Features

  • update references to point to hashicorp module registry (#414) (a8e5e2d)

v6.6.2

12 Jun 13:12
5c7567b

Choose a tag to compare

6.6.2 (2023-06-12)

Bug Fixes

  • issue preventing from creating a COS instance only with authorization policy (#410) (5c7567b)

Any consumer using multiple modules to create encrypted buckets will need to add skip_iam_authorization_policy = true to all but the first encrypted bucket created. Since the policy will be associated with the first bucket, all subsequent buckets, will need to depend on the first one.

Any consumer creating a COS instance with existing_kms_instance_guid and then creating encrypted bucket(s) later will need to move the existing_kms_instance_guid onto the first bucket to be created.