-
Couldn't load subscription status.
- Fork 3
feat: updated KMS auth policy scope to scope to the KMS key + cleanup #313
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
|
/run pipeline |
|
As expected the upgrade test failed as it wants to recreate the auth policy. But it also failed on this update and no idea why... I'm going to have to do a manual upgrade test to figure this out |
|
OK after doing manual check, I see why the update is happening. Its because I updated the default COS endpoint to be the direct endpoint instead of public one: This is also expected, and non disruptive, so skipping upgrade test. |
|
/run pipeline |
|
|
|
/run pipeline |
|
/run pipeline |
|
@Ak-sky I addressed the issues, and also added more tests. Can you please re-review? |
…-event-notifications into auth
|
/run pipeline |
1 similar comment
|
/run pipeline |
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.
Just some minor changes related to the code comments.
Rest everything looks good to me.
solutions/standard/main.tf
Outdated
| # If a prefix value is passed, add it to the COS key ring name | ||
| cos_key_ring_name = var.prefix != null ? "${var.prefix}-${var.cos_key_ring_name}" : var.cos_key_ring_name | ||
| # Determine the COS KMS key CRN (new key or existing key). It will only have a value if not using an existing bucket or existing EN instance | ||
| # cos_kms_key_crn = var.existing_cos_bucket_name != null ? null : var.existing_kms_root_key_crn != null ? var.existing_kms_root_key_crn : var.existing_en_instance_crn == null ? module.kms[0].keys[format("%s.%s", local.cos_key_ring_name, local.cos_key_name)].crn : null |
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.
We can remove this commented out code, right?
| # cos_kms_key_crn = var.existing_cos_bucket_name != null ? null : var.existing_kms_root_key_crn != null ? var.existing_kms_root_key_crn : var.existing_en_instance_crn == null ? module.kms[0].keys[format("%s.%s", local.cos_key_ring_name, local.cos_key_name)].crn : null | ||
| cos_kms_key_crn = var.existing_en_instance_crn != null || var.existing_cos_bucket_name != null ? null : var.existing_kms_root_key_crn != null ? var.existing_kms_root_key_crn : module.kms[0].keys[format("%s.%s", local.cos_key_ring_name, local.cos_key_name)].crn | ||
| # If existing KMS instance CRN passed, parse the account ID from it | ||
| cos_kms_key_id = local.cos_kms_key_crn != null ? module.cos_kms_key_crn_parser[0].resource : null |
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.
The above comment mentions about parsing the account ID, but we are getting the key_id.
solutions/standard/main.tf
Outdated
| validate_sm_crn = length(var.service_credential_secrets) > 0 && var.existing_secrets_manager_instance_crn == null ? tobool("'existing_secrets_manager_instance_crn' is required when adding service credentials with the 'service_credential_secrets' input.") : false | ||
| # parse SM GUID from CRN | ||
| existing_secrets_manager_instance_guid = var.existing_secrets_manager_instance_crn != null ? module.existing_sm_crn_parser[0].service_instance : null | ||
| # parse SM regiob from CRN |
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.
SM regiob -> SM region
|
/run pipeline |
|
🎉 This PR is included in version 1.13.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
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