- Notifications
You must be signed in to change notification settings - Fork 2
fix: cleanup the KMS validation logic + other cleanup #186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
SirSpidey left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
| PR test failing - need to skip upgrade test for this PR |
| Right, the upgrade test is failing due to a but thats fixed in this PR. Let me locally confirm the "complete" example is working well, and ill push a commit to this PR to skip upgrade test |
| 🎉 This PR is included in version 3.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
member_cpu_countnow defaults to 0 (meaning shared CPU)kms_encryption_enabledmust now be set if you want to use BYOK or KYOK encryptionskip_iam_authorization_policynow defaults totrue, but is only relevant ifkms_encryption_enabledis set to atrueFSCloud profile specific changes:
backup_encryption_key_crnis no longer a supported variable since it doesn't support HPCS (profile defaults to ICD randonly generated encryption key)crnoutputservice_credential_names(to create service credentials) andauto_scalingto enable auto scalingNOTE: I had to skip the upgrade test due to a bug that is currently in main branch, but is fixed in this PR. I manually ran the complete example (which is used during upgrade test) and it passed
Types of changes in this PR
Changes that affect the core Terraform module or submodules
Changes that don't affect the core Terraform module or submodules
Release required?
Identify the type of release. For information about the changes in a semantic versioning release, see Release versioning.
x.x.X)x.X.x)X.x.x)Release notes content
member_cpu_countnow supports0(meaning shared CPU). This is now the default value, so take note that when updating from a previous version, you may now wish to explicitly set this to match (or update the current value)membersnow has a default value of 2 (was previously 3).kms_encryption_enabledmust now be set if you want to use BYOK or KYOK encryptionskip_iam_authorization_policynow defaults totrue, but is only relevant ifkms_encryption_enabledis set to atrueallowlisthas been removed as its now a legacy. The recommendation is to use CBRs instead.FSCloud profile specific changes:
backup_encryption_key_crnis no longer a supported variable since it doesn't support HPCS (profile defaults to ICD randomly generated encryption key)crnoutputmembersnow has a default value of 2 (was previously 3).Checklist for reviewers
Merge actions for mergers