Releases: terraform-ibm-modules/terraform-ibm-cos
Releases · terraform-ibm-modules/terraform-ibm-cos
v7.4.0
v7.3.2
v7.3.1
v7.3.0
v7.2.2
7.2.2 (2024-01-26)
Bug Fixes
- delay before using auth policy which is required as a workaround for this provider issue. NOTE: Upgrades from earlier to version to this version may show a time_sleep.wait_for_authorization_policy being deleted if they are skipping authorisation policy creation. This is expected, since there is no need to delay if the authorisation policy already exists. (#518) (472a353)
v7.2.1
v7.2.0
7.2.0 (2024-01-23)
Features
- add support for the COS module creating a resource key for IAM only, or a resource key for IAM and HMAC.
The following input variables are renamed:
-create_hmac_key
->create_resource_key
-hmac_key_name
->resource_key_name
- hmac_key_role -> resource_key_role
A new input variable is introduced:generate-hmac-credentials
By defaultgenerate-hmac-credentials
is false and an IAM only resource key is created. Change the value totrue
to generate an IAM and HMAC resource key. Note: This is a change in behavior, previously the default option was to generate an resource key containing both IAM and HMAC keys.
When deploying for the first time at this level, everything is deployed as expected on the first apply.
When upgrading and requiring the IAM and HMAC resource key, the upgrade sequence should be to two deploys. The first deploy should rename existing properties. Then apply. Then add generate-hmac-credentials = true. Then apply. During the first apply some new terraform_data resources are created, during the second deploy the resource key is upgraded in place.
When upgrading and requiring an IAM only resource key, the upgrade sequence may not remove the HMAC key from resource key in the state file; but the IAM key is still present. This will correct itself later, or to force the removal; add generate-hmac-credentials = true. Then apply. Then remove generate-hmac-credentials and apply again. Both applies will be upgrade in place. (#506) (f5db77c)
v7.1.6
v7.1.5
v7.1.4
7.1.4 (2024-01-02)
Bug Fixes
- removed input variables
sysdig_crn
andactivity_tracker_crn
from the fscloud submodule as they were unused. If you wish to set a bucket up with metrics or activity tracking, use the optionalactivity_tracking
andmetrics_monitoring
options in thebucket_configs
input variable, as demonstrated in the fscloud example (#490) (00eeab4)