v1.26.0
·
105 commits
to main
since this release
1.26.0 (2025-03-25)
Features
- The KMS auth policy has been updated so its now scoped to the exact KMS key. If upgrading from an older version this will recreate the auth policy, however it will create the new one before destroying the old one so there is no disruption to every day services.
- The
kms_instance_guidinput has been removed from the module. It is now programmatically determined from the value ofkms_key_crn - A new boolean input
is_hpcs_keyhas been added to the module and should be set totrueif the key specified inkms_key_crnis from a Hyper Protect instance. Leave it at false if using Key Protect. If set to true, a second auth policy is created which allows the Secrets Manager instance Viewer access to the HPCS instance.