-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: use external kms key #131
Conversation
/run pipeline |
/run pipeline |
@kierramarie ensure changes (including variable descriptions) are consistent with terraform-ibm-modules/terraform-ibm-secrets-manager#147 |
@ocofaigh this da uses kms for en and cos. should I update the cos part as well to use the external kms (I have already mostly implemented this)? |
@kierramarie I don't get you - EN is not deployed in this DA? This is the SCC DA, so KMS key is only used to encrypt the COS bucket used by SCC |
sorry wrong PR 🤦♀️ |
/run pipeline |
It appears that the upgrade test is failing because the iam policy is being changed. Is it okay to skip upgrade test? |
/run pipeline |
@kierramarie why iam policy has been changed? do we know the reason? I guess, if we are not creating cross account policy, then settings for previous iam policy shouldn't change |
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.
see comments
@akocbek here is what I get when I run the upgrade test:
I am unsure of what exactly is changing but it seems to be doing an update to the policy. |
We should not be touching the auth policy being created in cos module, so this needs to be debugged to find out why its updating - suggest to recreate locally |
@ocofaigh From what I understand |
But @kierramarie The test is not setting any value for |
@ocofaigh this is what I got when I ran locally. Its not actually changing but is triggering an update for some reason:
|
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.
@ocofaigh is my assumption that if a user passes an existing scc instance, no kms variables are needed, correct? |
@kierramarie I think what we agreed was if user is passing an existing SCC, the assumption is its already configured with a COS bucket, and hence no KMS details are required, since we only use KMS to encrypt the COS bucket. |
/run pipeline |
@kierramarie can you address the failures here please? |
/run pipeline |
/run pipeline |
This is why the upgrade test is failing:
|
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.
/run pipeline |
🎉 This PR is included in version 1.22.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
An external kms key can be used now. If an api key for the external account is passed, new iam policies will be created for COS to communicate with the external kms instance.
Git Issue: #107
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers