Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: terraform-ibm-modules/terraform-ibm-event-streams
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v3.0.2
Choose a base ref
...
head repository: terraform-ibm-modules/terraform-ibm-event-streams
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.1.0
Choose a head ref
  • 1 commit
  • 26 files changed
  • 1 contributor

Commits on Dec 18, 2024

  1. feat: Root module updates:<br>- existing_kms_instance_guid is no lo… 

    …nger a supported input. The code will now parse the GUID from the KMS key CRN<br>- added new input `use_same_kms_key_for_backups` to give more control over KMS key usage<br>- `kms_encryption_enabled` has been renamed to `use_ibm_owned_encryption_key`<br>- `fscloud` submodule updates:<br>- added new inputs `use_default_backup_encryption_key` and `use_same_kms_key_for_backups`<br>DA updates<br>- 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.<br>- The `skip_iam_authorization_policy` input has been renamed to `skip_es_kms_auth_policy`<br> 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)
    @akocbek
    akocbek authored Dec 18, 2024
    Configuration menu
    Copy the full SHA
    e7598e2 View commit details
    Browse the repository at this point in the history
Loading