Releases: terraform-ibm-modules/terraform-ibm-icd-redis
Releases · terraform-ibm-modules/terraform-ibm-icd-redis
v1.17.3
v1.17.2
v1.17.1
v1.17.0
1.17.0 (2025-01-31)
Features
- updated the
service_credential_secrets
input object schema of the DA to support creating service specific roles
* Theservice_credentials_source_service_role
attribute has been renamed toservice_credentials_source_service_role_crn
and now requires a full CRN value. For example: `service_credentials_source_service_role_crn = "crn:v1:bluemix:public:iam::::role:Editor" (#510) (a4e04b6)
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
1.16.0 (2025-01-15)
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 touse_ibm_owned_encryption_key
fscloud
submodule updates:- added new inputs
use_default_backup_encryption_key
anduse_same_kms_key_for_backups
- added new inputs
- DA updates:
- Removed the input
existing_backup_kms_instance_crn
. If you want to use a different KMS key for backups, you can use theexisting_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. - 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.
- Removed the input