-
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
Pre wired cbr #262
Pre wired cbr #262
Conversation
/run pipeline |
1 similar comment
/run pipeline |
/run pipeline |
1 similar comment
/run pipeline |
/run pipeline |
1 similar comment
/run pipeline |
/run pipeline |
@@ -51,14 +51,15 @@ locals { | |||
# Merge zone ids to pass as contexts to the rule | |||
target_services_details = [ | |||
{ | |||
target_service_name = "kms", | |||
target_service_name = "secrets-manager", |
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.
Made changes in target service from "kms" to "secrets-manager" in this example because in fscloud example same resource group (geretain-test-cbr) was used to create rule for kms
as the pipeline tests were failing with A rule with the same resource attributes already exists
.
Thanks @Ak-sky - I put some more comments at #222 (comment) based on latest direction with consumers this week. Also this address the open design question on how consumer can add their own rules on top of the one pre-set for fscloud. |
Continued in #267 |
Description
Pre-wired CBR configuration for fs cloud
fixes #259 and #222
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
If a release is required, replace this text with information that users need to know about the release. Write the release notes to help users understand the changes, and include information about how to update from the previous version.
Your notes help the merger write the commit message for the PR that is published in the release notes for the module.
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
Merge actions for mergers