-
Notifications
You must be signed in to change notification settings - Fork 0
fix: updated cloud log mapping #69
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
|
Any update? This is currently blocking some other DAs from consuming new Observability DAs |
|
/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.
I don't think you need to map existing_kms_instance_crn and existing_kms_key_crn in the Cloud Logs dependency config - Cloud logs DA will have its own mapping to KMS already.
I think the same might be true for existing_cos_instance_crn - Cloud Logs DA already has its own mapping for COS.
Can we do some testing to confirm this?
|
/run pipeline |
|
/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.
deploy-arch-ibm-account-infra-base should not be a dependant DA - the AT DA doesn’t use resource group like we discussed yesterday
|
/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.
See 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.
We need to make the exact same changes for COS:
enable_activity_tracker_event_routing_to_cos_bucketshould be false in the terraform DA code, and we should set it to true in the mapping if COS DA is enabled- Variable validation should be added for
existing_cos_instance_crnto make sure its notnullifenable_activity_tracker_event_routing_to_cos_bucketis true
solutions/fully-configurable/catalogValidationValues.json.template
Outdated
Show resolved
Hide resolved
|
/run pipeline |
| "prefix": $PREFIX, | ||
| "existing_cos_instance_crn": $COS_INSTANCE_CRN, | ||
| "existing_resource_group_name": "geretain-test-resources" | ||
| "enable_activity_tracker_event_routing_to_cloud_logs": true, |
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 If we have enabled it to true, wouldn't the catalog validation while publishing the tile will fail based on the validation we just added?
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.
No we are creating ICL and COS in tests/resources/main.tf
|
🎉 This PR is included in version 1.2.11 🎉 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